-
Notifications
You must be signed in to change notification settings - Fork 208
SwiftDriverExecution: add explicit dependency on libllbuild #1957
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The module directly imports libllbuild, and while the dependency _should_ be available due to the dependency on `llbuildSwift`, this ensures that we do not rely on ordering but rather the explicit dependency is codified into the build graph.
@swift-ci please test |
`llbuild` is imported always. Simply import that unconditionally.
The value needs to be pushed through the cache as there is no control over the flags for the sub-build and `set` is scoped to the current directory.
@swift-ci please test |
@swift-ci please test Windows platform |
Please test with following PRs: @swift-ci please test Windows platform |
LLDB test hung it seems ... |
Please test with following PRs: @swift-ci please test Windows platform |
1 similar comment
Please test with following PRs: @swift-ci please test Windows platform |
@swift-ci please test Windows platform |
@swift-ci please test Windows platform |
The module directly imports libllbuild, and while the dependency should be available due to the dependency on
llbuildSwift
, this ensures that we do not rely on ordering but rather the explicit dependency is codified into the build graph.