Skip to content

Conversation

@kateinoigakukun
Copy link
Member

Even with unified build, llvm is not always the top-level project but it can be a part of a larger build. In such cases, CMAKE_BINARY_DIR is not the same as LLVM_BINARY_DIR but swift side expects features.json is in LLVM_BINARY_DIR1.

Footnotes

  1. https://github.com/swiftlang/swift/blob/swift-DEVELOPMENT-SNAPSHOT-2025-02-14-a/lib/Option/CMakeLists.txt#L11

…BINARY_DIR`

Even with unified build, llvm is not always the top-level project but it
can be a part of a larger build. In such cases, `CMAKE_BINARY_DIR` is
not the same as `LLVM_BINARY_DIR` but swift side expects `features.json`
is in `LLVM_BINARY_DIR`[^1].

[1]: https://github.com/swiftlang/swift/blob/swift-DEVELOPMENT-SNAPSHOT-2025-02-14-a/lib/Option/CMakeLists.txt#L11
@kateinoigakukun kateinoigakukun requested a review from a team as a code owner February 16, 2025 02:17
@kateinoigakukun
Copy link
Member Author

@swift-ci test

@kateinoigakukun
Copy link
Member Author

@swift-ci test Windows

@kateinoigakukun
Copy link
Member Author

@swift-ci test macOS

1 similar comment
@kateinoigakukun
Copy link
Member Author

@swift-ci test macOS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant