On Nov 1, 2007, at 7:29 AM, Jesper Eskilson wrote:
Andreas Pakulat wrote:
On 01.11.07 10:49:12, Jesper Eskilson wrote:
In any case, the automatic regeneration of project files *does*
*not*
*work*, and my question was simply if there was a plan for either
doing
something about it (such as disabling it per default, which would
be a
sensible thing to do, IMHO), and/or documenting that it is broken.
So far you're the only one claiming that (in this thread), I
suggest to
come up with a small sample project where changing the CMakeLists.txt
doesn't trigger a cmake run. If you've got that you can file a
bugreport
against cmake.
Did you actually read my post before replying?
I'm not claiming that cmake does not regenerate the project files. I'm
not claiming that Visual Studio does not reload the projects files.
What
I'm claiming is that ***the project files aren't reloaded until the
build already has completed***, meaning that I need to build
***again***
to make sure that the changes to my CMakeLists.txt actually make it
into
Visual Studio.
What is the desired behavior?
Did you want CMake to somehow notify the user that your project build
is incomplete and to build again?
Did you want CMake to stop after rebuilding project files, notify the
user, then only build the code if the project files weren't modified?
James
_______________________________________________
CMake mailing list
[email protected]
http://www.cmake.org/mailman/listinfo/cmake
