I'm actually pretty sure that it is expected behavior for the CUDA system in Visual Studio - look in the documentation for the findcuda.cmake file to double check. It has something to do with the multi-step, multi-target compilation process. It does seem rather strange, but I recall seeing an explanation that made it make sense to me.<div>
<br></div><div>Ryan<br><br><div class="gmail_quote">On Fri, Jan 14, 2011 at 12:05 PM, Patrick Charrier <span dir="ltr"><<a href="mailto:patrick.charrier@igd.fraunhofer.de">patrick.charrier@igd.fraunhofer.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi all,<br>
<br>
I am experiencing some (random) reloading of VS-project files and<br>
rebuilding when using the combination of CMake, Visual Studio and CUDA.<br>
<br>
Particularly when performing the following steps.<br>
1. Project has been built before.<br>
2. Perform an SVN update.<br>
3. Start CMake. Configure and Generate.<br>
4. Open the generated VS Solution.<br>
5. Build in Debug Mode. (Or Rebuild All.)<br>
6. Build in Release Mode. (Or Rebuild All.)<br>
<br>
After Point 6 the fun part starts.<br>
7. At this point VS runs CMake Configuration and Generation. Why this in<br>
the first place?<br>
8. VS will then ask to reload the newly generated VS-project files for all<br>
the CUDA VS-projects (libraries) in the solution.<br>
9. I hit yes and the project is being built.<br>
10. When trying to start the application, VS will prompt me to reload the<br>
VS-project files again, as in step 8.<br>
11. I hit yes again, but this time VS just says:<br>
1>------ Skipped Build: Project: PACKAGE, Configuration: Release Win32 ------<br>
1>Project not selected to build for this solution configuration<br>
2>------ Skipped Build: Project: INSTALL, Configuration: Release Win32 ------<br>
2>Project not selected to build for this solution configuration<br>
========== Build: 0 succeeded, 0 failed, 7 up-to-date, 2 skipped ==========<br>
<br>
The problem only occurs with CUDA and VS from what I know.<br>
My main question is, why is there a Reconfiguration and Regeneration in<br>
step 7, and how can I avoid it? There should be no need for it, since step<br>
3 should assure that the project files are fresh. Also why did it build<br>
smoothly in Debug (step 5), but not Release (step 6)?<br>
Also, what does the second Regenerate in step 11 mean?<br>
<br>
My guess is, that step 7 is somehow caused by Debug and Release sharing<br>
the same CUDA ".depend" and ".cmake" files in the CMakeFiles subdirectory of<br>
each CUDA VS-project. But how exactly, and how could I fix that?<br>
<br>
Thank you and Best Regards,<br>
Patrick<br>
<br>
<br>
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the CMake FAQ at: <a href="http://www.cmake.org/Wiki/CMake_FAQ" target="_blank">http://www.cmake.org/Wiki/CMake_FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.cmake.org/mailman/listinfo/cmake" target="_blank">http://www.cmake.org/mailman/listinfo/cmake</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Ryan Pavlik<br>HCI Graduate Student<br>Virtual Reality Applications Center<br>Iowa State University<br><br><a href="mailto:rpavlik@iastate.edu">rpavlik@iastate.edu</a><br>
<a href="http://academic.cleardefinition.com">http://academic.cleardefinition.com</a><br>Internal VRAC/HCI Site: <a href="http://tinyurl.com/rpavlik">http://tinyurl.com/rpavlik</a><br>
</div>