Export Swift binary from standalone toolchain - #1896
Merged
Conversation
adincebic
requested review from
aaronsky,
brentleyjones,
keith and
luispadron
as code owners
September 9, 2026 04:56
aaronsky
approved these changes
Sep 9, 2026
This file contains hidden or 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
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.
Allowing Swift binary to be invoked from things like rules_swift_package_manager.
Currently the rules_swift_package_manager invokes
swift packageduring loading phase which fails with standalone Swift toolchain because it can't findswifton the path.To work around that, we are allowing Swift binary to be injected by the consumer:
Referencing
@swift_toolchain_ubuntu22.04//:usr/bin/swiftcurrently fails because theswiftbinary needs to be exported.Example usage in cgrindel/rules_swift_package_manager#2511