Xcode 11 and Swift 5.1 support #67
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
|
Update: I found a more elegant solution for the missing dylibs that also passes pod linting. Still unclear why this became an issue in Xcode 11 though! |
kyleve
approved these changes
Mar 23, 2020
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.
This updates the Travis config to build with Xcode 11, which means Swift 5.1 features are now supported.
Unfortunately, this required a kludge to get tests working on 32-bit simulators. For some reason, the builtin
swift-stdlib-toolin Xcode 11 does not copy all the swift stdlibs into the xctest bundle. This PR contains a workaround that just adds the stdlib directory to the runtime search paths instead of copying them.