I ran into an odd problem today while trying to compile a test plugin. I get an error message stating that at least one of the module paths is not set. Strangely, this worked until recently and I don’t see anything that would likely cause this problem.
Note: I confirmed that all of the module paths make sense (see further down) & this project does compile with no problems when done directly in Xcode 10.
The script:
echo "resave and compile"
/Applications/Projucer.app/Contents/MacOS/Projucer --resave $HOME/Documents/SourceControl/SineSynth/SineSynth.jucer
/Applications/Projucer.app/Contents/MacOS/Projucer --resave-resources $HOME/Documents/SourceControl/SineSynth/SineSynth.jucer
cd $HOME/Documents/SourceControl/SineSynth/Builds/MacOSX/
xcodebuild -project SineSynth.xcodeproj -configuration Debug
The error message:
resave and compile
Re-saving file: /Users/me/Documents/SourceControl/SineSynth/SineSynth.jucer
Error when saving: At least one of your JUCE module paths is invalid!
Please go to the Modules settings page and ensure each path points to the correct JUCE modules folder.
The module path is shown here & is the same for all modules:
You have “Use global path for this module” checked. You need to verify that the global paths (in Projucer > Global Paths) make sense as well, or you need to uncheck “Use global path for this module” to use the path specified in the field above.
Thank you McMartin. They are set in the way that makes sense, I believe…that is why this is so strange. Unless I am misunderstanding something, of course.
Please try to add one module with “Add a module from a specified folder” button, I had also a very awkward problem, which was gone once I used this function.
@anoesisaudio
I did the same but it did not solve my problem. The exact same error persists. So did you check the use Global Paths checkbox again after adding the modules or yo left it unchecked?
Thanks
I actually removed the checkbox for Global Path and then used absolute path and that solved the issue. Thanks a lot. I have not used the cmake but I will check that out too.
There’s also a thing, I think, where if you add your JUCE folder (without /modules) to the modules path it looks like it’s going to work and you get a green light from the Projucer but then when you run it in the IDE it can’t find things, e.g.