And, if you look at my dspfilters open source library, you will see that the three projects (the juce amalgamation, the dspfilters library, and the demo app) all have shared settings via XCode 4’s .xcconfig files:
dspfilters also uses property sheets for Visual Studio so you can look at that as an example, as well:
So basically you are saying use IntroJucer, a separate application and additional step in the build process, to accomplish that which can already be done using the features built-in to both development environments, because you can’t be bothered to learn all the features of the IDE?
This is exactly why I want control over my project file, and why I do not want to depend on an additional tool to put my projects together. For the same reason I use C++ - I want total control over my projects so that I can optimize them fully to accomplish my goals.
Thumbs up to a better organization for Juce source files and modularized include structure, but thumbs down to requiring IntroJucer! And thumbs down to .cpp files which don’t get compiled - Qt Creator IDE does not have this feature of being able to disable .cpp files from compilation but still have them show up in the IDE, so we have taken a backward step in compatibility.