Fix Swift PM compatibility by creating a separate ObjC target #428
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 compatibility got broken after adding Objective-C source code #415 . There are multiple ways to fix it:
While I think making this project Swift-only is better, I made this PR to just fix the Swift Package Manager while keeping the implementation intact.
Other changes are targeted to fix the bundled resources that were not available in the Swift Package #400 . And to make sure that the framework can still be build from the project file (conditional imports are used for Swift PM or project compilation).
For me it has solved the Swift Package Manager problems, but I didn't check if CocoaPods and Carthage work. I did check that the project file allows to build the framework though.