Using Xcode and Projucer 4.3.0.
I noticed that if I check the “Create local copy” only for some modules, then in the “Build settings” I have the following Header Search Paths:
../../JuceLibraryCode ../../../juce/modules ../../JuceLibraryCode/modules
The problem is that the include path for the locally copied modules (
../../JuceLibraryCode/modules) comes after the one for those in the main JUCE folder (which live in
This means that, when the corresponding file in the JuceLibraryCode is processed (for example, the follwing:)
/* IMPORTANT! This file is auto-generated each time you save your project - if you alter its contents, your changes may be overwritten! */ #include "AppConfig.h" #include <juce_opengl/juce_opengl.mm>
juce_opengl/juce_opengl.mm module that is included is not the locally copied one (inside
../../JuceLibraryCode/modules), but still the one inside the main JUCE source code at
I think this kinda misses the whole point of having local copies of the modules.
I suggest adjusting the Projucer so that the Header Search Paths for the local copies come before the one for modules inside the main JUCE code.