> A good rule of thumb is to try just upgrading CMake and running it on > existing build trees. It's obviously quicker than a re-configure from > scratch. > > But then, before complaining about something not working, try it in a fresh > build tree first, then if it's still wrong, complain. :-) > > It's rare, although it does happen sometimes, that we make a change in CMake > itself that invalidates something that's in an existing cache. >
Fully agreed.. It has been quite rare that a CMake upgrade has caused a problem or a need to re configure. John -- 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
