On Tue, 2018-12-18 at 14:10 -0500, frodak17 wrote:
> How does this work with multiple languages and the project() command
> and enable_language() commands?
Both project() and enable_language() could be extended with an optional
TOOLCHAIN argument.
> For instance you want to use the host c++ compiler and a toolchain
> specified compiler for c and c++.
> When project() enables the c++ compiler it runs through a bunch of scripts to
> find and test the compiler also setting several CMAKE__* variables to use
> that compiler. These variables also happen to be the default compile options
> for the build types when using that compiler.
The point of this idea is to get rid of the old variable-based system
and have everything instead be a property of a toolchain. So the
scripts would set properties of the default toolchain instead of
setting variables.
> Then the same thing happens with the tool-chain specified compiler
> for these languages how do you track that the variables are different
> for these two toolchains?
> Are these variables now project scoped and for any given project it
> is limited to one toolchain per language per project?
>
See above.
Kyle
--
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
