Declare framework dependencies in podspec #773
Merged
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.
Users may want to build the pod with Clang modules disabled using
-fno-modules
/CLANG_ENABLE_MODULES=NO
because they are using ccache which doesn't support -fmodules. When modules are disabled, auto-linking of framework modules is also disabled, so these dependencies need to be expressed explicitly.What does this PR do?
Declares all the frameworks the pod depends on explicitly in the podspec, so that users may disable 'Clang Modules' in order to build the Objective-C code using
ccache
for faster builds. WhenCLANG_ENABLE_MODULES
is off, automatic framework linking is also implicitly turned off, so without this declaration the pod no longer links.Where should the reviewer start?
Review that all frameworks listed are used in the pod.
How should this be manually tested?
Perform
bundle exec pod install
of this podspec and ensure the pod still builds in the target.Questions:
No.
No, these are all Apple provided iOS frameworks.
No.
@segmentio/gateway