This way cmake will pick /usr/local/bin/cc or c++, which we
point to the appropriate compiler.
Details
Diff Detail
- Repository
- rZORG LLVM Github Zorg
- Build Status
Buildable 96276 Build 134889: arc lint + arc unit
Event Timeline
With this change the corresponding configurations will depend on the worker's internal set-up to use the desired compiler. IMO that's totally fine, provided that:
- linaro-aarch64-flang-latest-clang picks at least clang-11, and
- linaro-aarch64-flang-latest-gcc picks at least gcc-10.
But it is hard for me to review/check this without knowing the configuration of your workers. I'll defer to @maxim-kuvyrkov .
Personally I think that using CMake variables makes the configuration easier to reason about. Perhaps that's just implementation detail?
We set compiler for various bot configurations at https://git.linaro.org/ci/dockerfiles.git/tree/tcwg-base/tcwg-llvmbot/run.sh#n61 .
Personally I think that using CMake variables makes the configuration easier to reason about. Perhaps that's just implementation detail?
We have experimented with this, and using CMake variables ...
... made it hard to experiment with new compiler versions for periodic updates
... made it tricky to use ccache consistently, especially for 2-stage builds.
So we decided to use rely on default cmake behavior of picking up /usr/local/bin/cc and /usr/local/bin/c++ for the compilers, and point these wrappers to specific compiler we want to use.