Consolidate targets in the xcodeproj into a single target#1063
Merged
Consolidate targets in the xcodeproj into a single target#1063
Conversation
8f57cc4 to
536a6e5
Compare
This was referenced Sep 26, 2023
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.
Fixes #1062
Makes it easier to maintain the xcodeproj and adding new platforms (sup visionOS) by consolidating our multiple, platform-dependent targets into a single Nimble target (plus one for NimbleTests).
This breaks the public API: People who embed the xcodeproj (i.e. using git submodules) will need to specify the Nimble xcframework. Also, people who use Carthage (and are using intel) will now have to use the
--use-xcframeworksoption.