On Mon, Nov 24, 2008 at 12:28 PM, Bill Hoffman <span dir="ltr"><<a href="mailto:bill.hoffman@kitware.com">bill.hoffman@kitware.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Robert Dailey wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
The only trouble these projects are causing me is clutter. There is no functional purpose for them as far as I know, which is another reason why I do not like them.<br>
</blockquote></div>
You could try this:<br>
<br>
set(CMAKE_SUPPRESS_REGENERATION TRUE)<br>
<br>
I think that will get rid of ZERO_CHECK, but I am not sure. Again, this will potentially break your builds, and make them less reliable. ZERO_CHECK is used to make sure that the project files are up-to-date relative to the CMakeLists.txt files. It is also used to check some depend information that VS does not do.<div class="Ih2E3d">
<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
I'm not familiar with CTest. All I can say on that topic is that I've used Visual Studio for over 6 years and I've never had to use anything called CTest to get projects working.<br>
<br>
</blockquote></div>
CTest is the built in regression testing system of CMake. You can use it to create continuous testing integration for a project (see <a href="http://www.cdash.org" target="_blank">www.cdash.org</a>).</blockquote></div><br>
Ah, okay. If it manages synchronization between the CMakeLists.txt files and the vcproj files I can understand the need for them. I guess I should have first asked what they are for instead of immediately trying to get rid of them :)<br>
<br>Thanks for your help. I'll leave them be for now and just deal with the clutter. Of course, it would be great to be able to stuff some of these CMake files into a subdirectory of some sort so I don't have to see them clutter the CMakeLists.txt parent directory.<br>