-
Notifications
You must be signed in to change notification settings - Fork 263
Add watchOS, tvOS, iOS platforms support #176
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
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These
SDKROOT
changes are surprising to me. Can you explain what's going on here? This corresponds to theBase SDK
setting in the Xcode UI.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very good question!
Please note that most of the changes I made are based on PromiseKit and the article.
We also should note that we're making the multi-platform single-scheme framework now, so each platform needs it's own
SDKROOT
.I tried the same setup for
SDKROOT
as forPromiseKit
(just by removingSDKROOT
on project level) and it works forswift-corelibs-xctest
. But I had to add to specifySDKROOT
forSwiftXCTestFunctionalTests
target, because withoutSDKROOT
it failed to build.PS. I agree that it would be better having
SDKROOT
on project level for each platform, but Xcode only allows configuring it for architecture (I tried doing it via Xcode UI), not for platform.It would be awesome if you provide any better solution. Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my testing, Xcode will automatically adjust the
SDKROOT
used for a build such that it matches the platform of the run destination. For example, if the selected SDK is "Latest macOS" and the build has an iOS device destination selected, it will implicitly use the "Latest iOS" SDK instead. Therefore I would prefer keeping the Base SDK setting at the project level with no target overrides.One other minor point: I think it would be better to specify the new
SUPPORTED_PLATFORMS
value at the level of theSwiftXCTest
target, rather than at the project level, for now anyway. This is because theSwiftXCTestFunctionalTests
target only works on macOS, and I don't foresee that changing.Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the comments. I did the following updates: