I made a directory structure in parallel with the Juce directory. The modules were then found, but now when building, projucer complains it can’t find the mm files.
I’ve given up on this. Too many adjustments for a juce beginner to understand.
Why is this so difficult? There are no instructions on the tutorial page and the tutorials obviously are not being kept up to match the latest juce distribution.
Tutorials should be very easy for someone new to juce to download and run.
I am on the mac, in case anyone wants to give it a go and come up with some reasonable instructions on how to run the tutorials.
If you start from the projucer and the modules path is correct, you shouldn’t have to change anything…
Open the .jucer file - Click in the “Config” tab on “Save Project and open in IDE” - there you hit compile and run…
Any mm files are created and/or copied to the locations where they are needed in the projucer exporter, which is the one working when you hit “Save Project and open in IDE”.
Did you do it that way?
Create a directory where you downloaded JUCE to called ‘tutorials’
In the ‘tutorials’ directory, create another directory called ‘tutorials’.
Download any of the tutorials to the last ‘tutorials’ directory you created.
Run Projucer and open the jucer file of the tutorial you downloaded.
Now go to the projucer File menu and select 'save project’
This will cause projucer to copy the files to the JuceLibraryCode directory and start compiling
Wait for compile to complete.
From the projucer Build menu, select ‘Launch Application’
Get these instruction on the tutorials page and those new to JUCE won’t have to waste hours of their time.
I had the same experience as babazaroni. Very frustrating. Digging deeper I found most tutorials work exactly as martinrobinson described above, with a module path of “…/…/juce/modules”. But the first three graphics tutorials do not, enough to derail many newcomers:
tutorial_main_window.zip
tutorial_main_component.zip
tutorial_graphics_class.zip
These have a module path of “…/…/…/JUCE/modules”. tutorial_graphics_class.zip also has an extra directory layer “GraphicsTutorial” in the zip file. Fixing these inconsistencies, plus instructions on the set up, would remove a major pothole from the JUCE on-ramp
hth,
ch
ps It would also help to add a map of tutorial dependencies. For example, tutorial_simple_synth_noise looks first, and tutorial_synth_level_control looks next, except oops it assumes tutorial_slider_values, and oh wait that assumes tutorial_listeners_and_broadcasters.zip, and where does this rabbit hole really start anyway?
This problem could be reduced greatly by explaining how to set the module path correctly somewhere in the tutorials. This is not obvious for people who don’t know much about projucer and just want to run the tutorials.