-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Use SwiftBuild API to reliably compute built artifacts #9143
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
a5a1f06
to
3068ec7
Compare
} | ||
var name = target.name | ||
// FIXME: We need a better way to map between SwiftPM target/product names and PIF target names | ||
if pifTargetName.hasSuffix("-product") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems like an accident waiting to happen :S
Should we have some more API surface here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think so, but I haven't decided what it should look like yet
@swift-ci test |
3068ec7
to
b43f345
Compare
@swift-ci test |
@swift-ci test Windows |
@swift-ci test self hosted |
1 similar comment
@swift-ci test self hosted |
Depends on swiftlang/swift-build#801
By querying the build system for the artifacts, we ensure we only report any we will actually produce in the current build. At the same time, pull in an alternative fix for #9121 which restores the original behavior of the native build system when considering products in dependency packages.