<div class="gmail_quote">On Wed, Oct 26, 2011 at 4:42 PM, Dan Kegel <span dir="ltr"><<a href="mailto:dank@kegel.com">dank@kegel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I'm going over the checklist of whether cmake will meet<br>
the needs of my eclipse users, and their first question<br>
was what was the workflow for adding a new source<br>
file.<br>
<br>
I just tried the experiment of adding a .cpp file,<br>
adding it to CMakeLists.txt, and clicking Build...<br>
and the .o file showed up as it should have. This<br>
kind of surprised me, since I didn't re-run cmake.<br>
<br>
Is the generator smart enough to notice the<br>
changes to the CMake files and re-run cmake<br>
with the same environment variables and options<br>
as it was originally run with? I kind of doubt it.<br>
<br>
The cdt4 web page says<br>
"When you edit your CMakeLists.txt file, you are recommended to delete<br>
your project and reimport it."<br>
Is it assuming that you've rerun cmake manually?</blockquote><div><br></div><div>When you make any changes to any CMakeLists.txt, the Makefiles are setup to check this and invoke cmake to reconfigure and regenerate those makefile scripts. I only use Visual Studio generators, so I can't say exactly how it works for Makefiles, but the principle is the same between the two.</div>
<div><br></div><div>Basically there is no need to run cmake directly after each edit. I only run cmake once after a fresh checkout of my source code to get the initial scripts, then after that I let it automatically detect changes and do the respective work required to regenerate scripts/project files. </div>
</div>