AFAIK, normally there will be 3 xcconfig in your project if you use libgdx + cocoapods:
- custom.xcconfig which is used by libgdx to link libgdx’s native libs.
- Pods-[xcode nam].debug.xcconfig
- Pods-[xcode nam].release.xcconfig
2 and 3 are generated by cocoapods.
I have no idea where your build.xcconfig came from.
Before you add cocoapods support, your libgdx project should only have custom.xcconfig which is referenced from your xcodeproj.
After you add cocoapods, your xcodeproj should references Pods-[xcode nam].debug.xcconfig in debug config and Pods-[xcode nam].release.xcconfig in release config. But since your project already use custom.xcconfig that’s why you will get warning like this:
It suggests you to include Pods-[xcode nam].debug/release.xcconfig in custom.xcconfig but it’s usually a better idea to do in the opposite: include custom.xcconfig in Pods-[xcode nam].debug/release.xcconfig because the xcconfig for pods have two different configs (debug and release) and custom.xcconfig is shared between both two build configs. You can’t include xcconfigs for different build configs in the same file. Further more, the content of custom.xcconfig is generated during build process by libgdx (see here).
Here is an example (using the sample libgdx project from here):
-
Select the correct config for debug & release configs:
(Remember to add these two xcconfig files to your main project like highlighted on the left side.) -
Include custom.xcconfig in those files:
