Open sharplet opened 4 months ago
1 Warning | |
---|---|
:warning: | Please include a CHANGELOG entry to credit yourself! You can find it at CHANGELOG.md. |
Here's an example of your CHANGELOG entry:
* Add Support for Xcode 14.3's ENABLE_MODULE_VERIFIER
[sharplet](https://github.com/sharplet)
[#issue_number](https://github.com/CocoaPods/CocoaPods/issues/issue_number)
note: There are two invisible spaces after the entry's text.
Generated by :no_entry_sign: Danger
The module verifier validates framework modularity in a clean test environment that doesn't work out of the box with the way CocoaPods framework targets are installed in
CONFIGURATION_BUILD_DIR
. Specifically, Xcode's default behaviour is to build framework bundles directly in$(CONFIGURATION_BUILD_DIR)
, whereas pod framework targets are built in a nested directory$(PODS_CONFIGURATION_BUILD_DIR)/PodName/
. The result is that any Xcode framework target withENABLE_MODULE_VERIFIER
set toYES
will fail to locate pod framework headers when verifying modularity.By customizing
OTHER_MODULE_VERIFIER_FLAGS
, we can add pod framework build directories to the framework search path, allowing Xcode framework targets that depend on pod framework targets to use the module verifier.