Agreed that it is a bit heavyweight, but the stray files have resulted in
some pretty cryptic issues in the past (targets linking against an old
version of a library that got renamed etc...).
Your idea sounds good... I'll give it a try.
Thanks!
-=Abe
On Fri, Feb 14, 2014 at 8:55 AM, Bill
I'd only want to do a full build if one of the CMakeLists.txt has changed
(cmake needs to get re-run). Otherwise, I'd like to do a normal build.
On Thu, Feb 13, 2014 at 4:52 AM, Ian Liu Rodrigues ian.li...@gmail.comwrote:
You are correct that I would prefer that behavior, however I'd prefer
On 2/14/2014 11:00 AM, Abe Bachrach wrote:
I'd only want to do a full build if one of the CMakeLists.txt has
changed (cmake needs to get re-run). Otherwise, I'd like to do a normal
build.
That seems a bit over kill to me. I would rather have a few extra files
than having a complete clean done
You are correct that I would prefer that behavior, however I'd prefer to
go for safety (and do a full clean) until that more advanced logic can be
implemented... I am in fact using ninja, so hopefully that feature may come
down the pipe soon :-)
If you want a full build, why don't you just
Hi there,
The Makefile that cmake generates includes a rule to automatically re-run
cmake if any of the input CMakelists.txt files change.
Is there a way to configure this rule to have it run clean first?
Currently, if you change the name of an executable target (or library), it
will leave the
On 2014-02-12 11:35, Abe Bachrach wrote:
The Makefile that cmake generates includes a rule to automatically re-run
cmake if any of the input CMakelists.txt files change.
Currently, if you change the name of an executable target (or library), it
will leave the old file in the output location,
On Wed, Feb 12, 2014 at 8:53 AM, Matthew Woehlke
mw_tr...@users.sourceforge.net wrote:
What you really want is to record the old list of output files, re-run
CMake, then remove any files on that list that no longer have rules to
generate them. If you do a complete 'clean' you will delete and
