Workaround for wrong SDK in build process for Xcode15 #13
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
Closed
|
We also tested this change against Xcode 14.3.1 (and it still works on the older version). |
|
Great! Thank you very much! |
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.
After upgrading to Xcode15 we started seeing this warning:
using sysroot for 'iPhoneOS' but targeting 'MacOSX'followed by a bunch of C compilation errors and the build would fail.Added a workaround that injects the sysroot to the underlying C compiler which feels like it is a bug in
swift buildas one would expect the-sdkparameter to propagate down the toolchain, but it appears it does not.Fixes #11