What first cross my mind with '"utilities" needed for build' is when you have to build the cross-compiler in the first place before you build anything for the target. If so how do you handle verification of the tool-chain can build a working executable or library? Normally that is done at the time before project files are generated but it has to either be skipped or delayed because the toolchain doesn't even exist because it has to be built first by the host tools. For tool-chains that already exist on the host machine then add_toolchain() command is when you can test and verify its functionality?
So if you want to build both for host and cross toolchain you'll have to >> explicitely >> add_executable/library(MyLibrary TOOLCHAIN DEFAULT) >> add_executable/library(MyLibrary TOOLCHAIN CrossToolchain) >> > Do these targets automatically get separate binary directories so that the outputs don't overwrite each other? I assume this feature is limited only to ninja or makefile generators?
-- 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: https://cmake.org/mailman/listinfo/cmake-developers
