AppConfig.h visibility limited to .cpp files only?

Currently, AppConfig.h is included only in .cpp files and not in the Juce interfaces (.h files).

Can we rely on this staying the same, always? Or will there come a point where the Juce interface files (.h files) become conditionally compiled based on AppConfig.h settings?

Well, it’s always better not to include something if you don’t need to… Maybe one day there’ll be a header that does need to know about the config, and I guess I’ll worry about it when that happens!

Actually, I think juce_core should have #include “AppConfig.h”. It is an error to include any Juce headers in your application without first including AppConfig.h, since it could cause the Juce library code to compile differently than client code, see this post: