On Sat, 2009-07-25 at 18:37 +0200, Mathieu Malaterre wrote: > On Fri, Jul 24, 2009 at 11:05 PM, David Cole<[email protected]> wrote: > > ccmake . does not erase the cache. > > Yes, it does AFAIK. When you have conflicting compiler defined in let > say VTK and another set ITK, and you try to import them. Unless you > use CMAKE_OVERRIDE_COMPILER_MISMATCH, cmake will start deleting your > entries in the cache. >
That is compatible with my experience. > the only solution I found is to make sure to use cmake (not ccmake) > and pass the appropriate -DVTK_DIR option on the first configure. Once > this passed, you can use ccmake again. > Indeed - and some more like CMAKE_BUILD_TYPE. Only to have to use command line switches anyway pretty much ruins the idea of initial cache, does it not. best regards, Dominik > 2cts _______________________________________________ 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
