I used IntroJucer (!) for one of my AppletJUCE demonstration applications, and I run into this problem:
vf_core.h is my own module, it includes JUCE headers, like this:
#include "modules/juce_core/system/juce_TargetPlatform.h" #include "modules/juce_core/juce_core.h"
The problem is that IntroJucer doesn’t add the JUCE source tree location to the include paths. Instead, it creates some funky stub files and points the project there instead. Unfortunately this fails because juce_TargetPlatform.h is not one of the victims of impersonation (invasion of the source code body snatchers?).
The VFLib source code folder sits parallel to the JUCE source tree in the AppletJUCE repository:
Once again, the smallest deviation from the workflow that IntroJucer forces you into, results in odd behaviors.