On 02/10/2016 03:49 AM, Vania Joloboff wrote: > We have not yet moved to 3.5 but seeing this discussion, I am wondering > what we will have to do. In our project, we have several C and C++ cross > compilers and we want to compare them on selected benchmarks. We also > want to compare different compile options and different linking options. > We know for sure these cross compilers are working properly > and our technique today is roughly > > CMakeForceCompiler(A) > compile benchmarks with A (and various options) > CMakeForceCCompiler(B) > compile benchmarks with B > CMakeForceCompiler(C) > compile benchmarks with C > > Next, we run all the benchmarks and compare the results. > > How am I supposed to do that if CMakeForceCompiler() is deprecated ?
CMakeForceCompiler was meant for use in toolchain files. We do not support switching compilers within a single CMakeLists.txt file nor multiple toolchains in a single CMake run. Can you post a more complete example of what you're trying to do? It sounds like your sequence should be scripted externally and run CMake multiple times with separate build trees. -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://public.kitware.com/mailman/listinfo/cmake
