(Feature)|Add support for SwiftPM #8
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
bconway99
approved these changes
Nov 11, 2020
bartpowers
approved these changes
Nov 11, 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.
Summary
This adds support for SwiftPM 5.3 while also maintaining existing support for Carthage / CocoaPods:
publicHeadersPath. This includes_Privateand_Protectedheaders, which don't really provide much benefit to begin withNSBundleresolution attempts to access the generatedSWIFTPM_MODULE_BUNDLEif it exists, which is necessary for projects that link the target via SwiftPMTesting
Testing the compatibility of Carthage / CocoaPods / SwiftPM is unfortunately not self-contained. I've performed tests outside of this project to keep the scope maintainable.
The existing embedded demo application and tests should still run and pass.