Alexander Neundorf said the following on 2/6/2012 3:56 PM:
Would it be acceptable if cmake would rerun after every build ?
You could enforce that e.g. with a add_custom_command( POST_BUILD ... ) which
could e.g. touch CMakeCache.txt or something.
Better ideas ?
We're working in a client/server environment in a fairly agile
production environment; we need to have /all/ executables correctly
stamped with the revision they're sourced from.
So I kind of need it run before each build.
Further, one of my problems is that right now the variable gets cached
in CMakeCache.txt, so I have to delete CMakeCache.txt or do
cmake -DSubversion_FOUND=NO
or similar.
In the short term, I can just make it always rebuild the revision.h, but
that has the downside of causing it to /always/ rebuild the library that
includes it, causing all binaries to relink, and so on, which is fairly
time consuming (it's a very large project :)
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Follow this link to subscribe/unsubscribe:
http://www.cmake.org/mailman/listinfo/cmake
