diff options
| author | Romaric Jodin <rjodin@google.com> | 2025-10-16 13:18:19 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-10-16 13:18:19 +0200 |
| commit | 88b77073460d61c66d9d0d599e6afd7b1b82bc4e (patch) | |
| tree | debe3b469bb00356808104c311f9a0590def12b0 /llvm/unittests/Bitcode/DataLayoutUpgradeTest.cpp | |
| parent | 44c96926c5e866766398c604f39c038c70e38d77 (diff) | |
| download | llvm-88b77073460d61c66d9d0d599e6afd7b1b82bc4e.zip llvm-88b77073460d61c66d9d0d599e6afd7b1b82bc4e.tar.gz llvm-88b77073460d61c66d9d0d599e6afd7b1b82bc4e.tar.bz2 | |
fix clang_cmake_builddir (#161220)
When building llvm from a subdirectory (like clspv does)
`CMAKE_BINARY_DIR` is at the top of the build directory.
When building runtimes (libclc for example), the build fails looking for
clang (through `find_package` looking at `LLVM_BINARY_DIR` with
`NO_DEFAULT_PATH` & `NO_CMAKE_FIND_ROOT_PATH`) because clang is not in
`LLVM_BINARY_DIR`.
Fix that issue by setting `clang_cmake_builddir` the same way we set
`llvm_cmake_builddir` from `LLVM_BINARY_DIR`.
For default llvm build (using llvm as the main cmake project), it should
not change anything.
For standalone clang build, keep the actual value as libclc cannot be
built that way.
Diffstat (limited to 'llvm/unittests/Bitcode/DataLayoutUpgradeTest.cpp')
0 files changed, 0 insertions, 0 deletions
