Factor out the common parts of Clang bootstrap configuration into a separate
CMake module.
Details
- Reviewers
phosek MaskRay alexander-shaposhnikov
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
clang/CMakeLists.txt | ||
---|---|---|
899–906 | I don't think we need a dedicated keyword for each tool, I'd just pass these through CMAKE_ARGS. |
clang/cmake/modules/ClangBootstrap.cmake | ||
---|---|---|
11 | We usually use lowercase names. |
clang/cmake/modules/ClangBootstrap.cmake | ||
---|---|---|
11 | Thanks! I was a bit confused by CMake's case use (e.g. ExternalProject_Add) |
clang/cmake/modules/ClangBootstrap.cmake | ||
---|---|---|
11 | Were you planning to also use the single arguments list such as ARG_LINKER in the CMAKE_ARGS? Without it, I have to supply an override to CLANG_BOLT_INSTRUMENT_EXTRA_CMAKE_FLAGS so I can avoid using the gnu linker. |
clang/cmake/modules/ClangBootstrap.cmake | ||
---|---|---|
11 | Yes, I added those in the first version of the diff and just forgot to remove them. But as Peter mentioned:
I'm neutral about adding ARG_LINKER or setting it through EXTRA_CMAKE_FLAGS, but I think explicit overrides for each tool are a bit too verbose. |
No longer needed for Clang-BOLT. @thevinster – feel free to commandeer if it fits your needs.
I don't think we need a dedicated keyword for each tool, I'd just pass these through CMAKE_ARGS.