Repository navigation
Added SPM support - #436
Merged
Merged
Conversation
2 tasks
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
2 participants
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 Package Manager has some strict requirements to source files layout. We can gain SPM support with minimal project structure changes by applying an autogenerated layout based on symbolic links technics. SPM related files located under
spmfolder at the project's root. You should NEVER modify it manually nor include to Xcode's project.So in this PR:
minimal necessary changes to make it work were:
iPhoneOnlyfolder toPlatformSpecificscript which can autogenerate SPM compatible layout
some improvements over macCatalyst code availability.
basic CI workflow
NOTE: if this diff will be accepted the next tag should be in SemVer format since SPM may have problems resolving the version otherwise. (2.4.0
instead ofrelease-2.4)