-
Notifications
You must be signed in to change notification settings - Fork 254
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
Take run destinations into account for SwiftPM build targets #1288
Open
ahoppen
wants to merge
2
commits into
apple:main
Choose a base branch
from
ahoppen:background-index-build-plugin
base: main
Could not load branches
Branch not found: {{ refName }}
Could not load tags
Nothing to show
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
ahoppen
changed the title
Take run destinations into account for SwiftPM build targets 🚥 #swift-package-manager#7555
Take run destinations into account for SwiftPM build targets 🚥 swift-package-manager#7555
May 13, 2024
apple/swift-package-manager#7555 @swift-ci Please test |
hamishknight
approved these changes
May 14, 2024
ahoppen
changed the title
Take run destinations into account for SwiftPM build targets 🚥 swift-package-manager#7555
Take run destinations into account for SwiftPM build targets
May 14, 2024
ahoppen
force-pushed
the
background-index-build-plugin
branch
from
May 14, 2024 18:07
8e73928
to
1841c62
Compare
@swift-ci Please test |
We can have two targets with the same name in a SwiftPM workspace, one for a build target and one for the destination. We need to be able to tell them apart based on the run destination.
This allows us to fix a toolchain when using a `SwiftPMBuildSystem`, which is critical to ensure that a target gets prepared using the same toolchain that is used to index it and that is used for sourcekitd.
ahoppen
force-pushed
the
background-index-build-plugin
branch
from
May 14, 2024 22:00
1841c62
to
74b1f09
Compare
@swift-ci Please test |
@swift-ci Please test Windows |
1 similar comment
@swift-ci Please test Windows |
Blocked because SwiftPM non-deterministically builds a target for tools or the destination when invoking it using |
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.
Depends on apple/swift-package-manager#7555
We can have two targets with the same name in a SwiftPM workspace, one for a build target and one for the destination. We need to be able to tell them apart based on the run destination.