Skip to content

[Build] BuildPlan: Use Destination instead of BuildTriple to form… #7881

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

Merged

Conversation

xedin
Copy link
Contributor

@xedin xedin commented Aug 14, 2024

… per-module plugin output directory

Motivation:

This is an NFC since there are no observable differences here from user perspective, just a different mechanism is used to get the same information.

Modifications:

  • computeDestinations provides a destination that should be used to invoke build tool plugins per module.

Result:

Removes one of the last places where BuildTriple was still used.

… per-module plugin output directory

Remove one of the last places where `BuildTriple` was still used.

This is an NFC since there are no observable differences here
from user perspective, just a different mechanism is used to
get the same information.
@xedin
Copy link
Contributor Author

xedin commented Aug 14, 2024

@swift-ci please test

@@ -786,7 +788,7 @@ extension BuildPlan {
components: [
package.identity.description,
module.name,
module.buildTriple.rawValue,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are there any remaining uses of buildTriple or can this property be removed now?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, we have a few more uses, mostly tests though. I'm planning to follow-up with SourceKitLSPAPI PR and then a PR to remove the rest.

@xedin
Copy link
Contributor Author

xedin commented Aug 16, 2024

@swift-ci please test

@xedin xedin merged commit 9456d16 into swiftlang:main Aug 16, 2024
5 checks passed
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.

2 participants