Fix module redefinition errors related to CommonCrypto and zlib #353
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.
When building Starscream in a project together with Kitura-WebSocket (or other IBM packages that use crypto), the compiler complains about there being two 'CommonCrypto' modules. See 'swift package show-dependencies' output:
This PR makes Starscream use the IBM module (which essentially is the same kind of wrapper around CommonCrypto as is daltoniam/common-crypto-spm), which resolves the issue (and leaves you with one less repository to maintain 🙂).