If the provided LLVM build-tree used a multi-configuration generator like Xcode, LLVM_TOOLS_BINARY_DIR will have a generator-specific placeholder to express CMAKE_CFG_INTDIR. Thus llvm-lit and llvm-tblgen won't be found.
D62878 exports the actual configuration types so we can fix the path and add them to the search paths for find_program().
Details
Details
- Reviewers
xiaobai labath stella.stamenova - Commits
- rGc76946243836: [CMake] Add configuration dirs as potential locations for llvm-lit and llvm…
rLLDB362589: [CMake] Add configuration dirs as potential locations for llvm-lit and llvm…
rL362589: [CMake] Add configuration dirs as potential locations for llvm-lit and llvm…
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
- Build Status
Buildable 32906 Build 32905: arc lint + arc unit
Event Timeline
Comment Actions
IIUC Clang uses the same mechanism. Moving append_configuration_directories() to AddLLVM.cmake could help there too. We may consider it for the future once D62859 is through.
lldb/cmake/modules/LLDBStandalone.cmake | ||
---|---|---|
67 | How is this working on Windows anyway? It should be llvm-tblgen.exe there right? |
lldb/cmake/modules/LLDBStandalone.cmake | ||
---|---|---|
67 | Ah, good point. You should use llvm-tblgen${HOST_EXECUTABLE_SUFFIX} as the name. That will add the suffix when required. |
lldb/cmake/modules/LLDBStandalone.cmake | ||
---|---|---|
67 | Ok added the suffix. I can imaging CMake would do it automatically if necessary, but it's not documented. |
How is this working on Windows anyway? It should be llvm-tblgen.exe there right?