There seems no way yet to include custom Xcode configuration with a Projucer project. Since xcconfig files support #include, they are great for uniformly maintaining multiple projects with a shared configuration base (version numbers, build locations, codesign signatures, deployment targets, stripping options, you name it).
The field Custom Xcode flags doesn’t work for including a xcconfig file (unless I missed something). It would be fantastic if there was a field Include Xcode config file instead. This would allow for arbitrarily complex build environments to nicely cooperate with Projucer.
Although CMake doesn’t support custom xconfig files, it does allow sharing common configuration options between targets. Would using CMake be a viable option for you?
Unfortunately not. However, I’ve made a workaround that doesn’t require JUCE to be included in our workspace as an xcodeproj, but rather as a pre-compiled dylib, so for me this is now more a “nice to have”.
CMake wouldn’t work for us unfortunately. The only reason I was asking is because I’ve been working on a project which makes use of the Conan Package Manager, but having to set the base configurations in the Xcode project each time I change something in the Projucer is really annoying.
