<html><head></head><body><div>On Tue, 2018-12-18 at 14:10 -0500, frodak17 wrote:</div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div>How does this work with multiple languages and the project() command and enable_language() commands?</div></div></div></blockquote><div><br></div><div>Both project() and enable_language() could be extended with an optional TOOLCHAIN argument.</div><div><br></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div>For instance you want to use the host c++ compiler and a toolchain specified compiler for c and c++.</div><div>When project() enables the c++ compiler it runs through a bunch of scripts to find and test the compiler also setting several CMAKE_<lang>_* variables to use that compiler. These variables also happen to be the default compile options for the build types when using that compiler.<br></div></div></div></blockquote><div><br></div><div>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.</div><div><br></div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><div>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?</div><div>Are these variables now project scoped and for any given project it is limited to one toolchain per language per project?</div></div></div>
</blockquote><div><br></div><div>See above.</div><div><br></div><div>Kyle</div></body></html>