On 01.05.2014 15:13, Rick McGuire wrote:
"clean build" referred to our existing system, not the cmake conversion. For our current system, it is only necssary to nuke the build output directory. Figuring out the mechanics of doing a switching mode under cmake is something we'll deal with once we're able to get the different kinds of build working.
So this was with a fresh (empty; specifically no CMakeCache.txt/CMakeFiles) build directory? The machine type is determined (and cached) the first time cmake runs for a build directory. It is determined by querying the compiler from within the environment in which it runs.
If this was with a clean build directory is it possible the project sets up custom compiler flags that would override the existing flags?
If that isn't the case either could you provide a minimal, self-contained test case that reproduces the issue?
Nils -- 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
