Support building with Xcode #14
Merged
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
Works around the lack of cross-compilation support in swift-build
kabiroberai
force-pushed
the
xcode-builder
branch
from
d737a25
to
f6e0c89
Compare
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.
swift builddoesn't support macros when cross-compiling, which is commonly needed for building universal macOS binaries (or even iOS if you're feeling frisky). Allow using xcodebuild to work around this. See: swiftlang/swift-package-manager#6950.Ideally, we would instead pass
--build-system xcodeto SwiftPM but that doesn't seem to support macros either.For easy viewing, I'd recommend looking at the PR diff with whitespace changes hidden.