-
Chris Brauchli authored
Whenever I run `pod install` I get warnings like: ``` [!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `TestClient` to `Pods/Target Support Files/Pods-TestClient/Pods-TestClient.debug.xcconfig` or include the `Pods/Target Support Files/Pods-TestClient/Pods-TestClient.debug.xcconfig` in your build configuration. ``` This is confusing, especially for people not familiar with CocoaPods. This adds a naive check for the CocoaPods-generated xcconfig being #included into the target's actual xcconfig. It also adds the ability to have a special token (I chose `// @COCOAPODS_SILENCE_WARNINGS@ //`, but am happy to change it) in the target's xcconfig to signal that the warning should be silenced even though CocoaPods's xcconfig does not appear to be included. This is useful for test targets and cases where the naive check is not sufficient.
2ab324a7
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
xcconfig_integrator_spec.rb |