[build] Stop assuming llvm is always the top-level in unified build #79342
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Even with unified build, llvm is not always the top-level project but it can be a part of a larger build. (e.g. [^1]) In that case, `CMAKE_BINARY_DIR` is not the binary directory of llvm but the binary directory of the top-level project. This patch fixes the issue by using `LLVM_BINARY_DIR` instead. [^1]: https://github.com/ChromeDevTools/devtools-frontend/blob/9b4b9070790196d78489756c515c528a0fe7ac00/extensions/cxx_debugging/CMakeLists.txt#L105
|
@swift-ci smoke test |
37 tasks
|
@swift-ci smoke test |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Even with unified build, llvm is not always the top-level project but it can be a part of a larger build. (e.g. 1) In that case,
CMAKE_BINARY_DIRis not the binary directory of llvm but the binary directory of the top-level project. This patch fixes the issue by usingLLVM_BINARY_DIRinstead.Footnotes
https://github.com/ChromeDevTools/devtools-frontend/blob/9b4b9070790196d78489756c515c528a0fe7ac00/extensions/cxx_debugging/CMakeLists.txt#L105 ↩