Hi, we eare using so far your nice effort here in this repository as external source, and we kind of reviewed it a bit. We came across the following:
-
Global variables NINJA_PATH should be documented what they are supposed to do, there are some more.
-
It would be really nice, to have only functions in your include cmake files , e.g. NuGet.cmake etc...
and include them and then use the functions in the corresponding toolchain. No global logic inside the includes, so that other users can also use these functions. IMO not good.
-
Maybe also structure the files into msc++ stands for MS standard library, not using Windows because its clear that this repo is about windows toolchains )
toolchain/msvc-msc++.cmake (wouldn't use multiple dots in filenames..)toolchain/clang-msc++.cmaketoolchain/clang-libstdc++.cmake (as a thought: tdm-gcc)
Includes:
toolchain/common/Ninja.cmake etc...toolchain/support/...
-
Another toolchain we were thinking of was
Would be cool to see these improvements.
Hi, we eare using so far your nice effort here in this repository as external source, and we kind of reviewed it a bit. We came across the following:
Global variables
NINJA_PATHshould be documented what they are supposed to do, there are some more.It would be really nice, to have only
functionsin your include cmake files , e.g. NuGet.cmake etc...and include them and then use the functions in the corresponding toolchain. No global logic inside the includes, so that other users can also use these functions. IMO not good.
Maybe also structure the files into msc++ stands for MS standard library, not using Windows because its clear that this repo is about windows toolchains )
toolchain/msvc-msc++.cmake(wouldn't use multiple dots in filenames..)toolchain/clang-msc++.cmaketoolchain/clang-libstdc++.cmake(as a thought: tdm-gcc)Includes:
toolchain/common/Ninja.cmakeetc...toolchain/support/...Another toolchain we were thinking of was
Would be cool to see these improvements.