On 11/04/2013 03:47 PM, David Cole wrote: > ccmake and cmake-gui *should* behave (in *my* opinion) as follows: > - on startup, load the CMakeCache.txt values (if there are any) from > the previous run > - then apply the -D arguments so that any -D arguments given on the > command line overwrite previous cache entries (just like command line > cmake does already) > - then put the user in charge and wait for user input > > This is, apparently, NOT the way that ccmake behaves today, but I think > it should be changed to be like that.
I agree, and there is not too much concern for compatibility in this case due to the use of an interactive workflow. -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
