This commit adds a new feature to the Projucer that has been on our backlog for some time - default module search paths. You can now specify a separate global path for both JUCE and user-created modules that will be used either as a fallback path when an exporter’s path field is empty (1) or by default if you select the “Use global path” option in the settings page of an individual module (2) or the “Enable/disable global path for all modules…” button in the main module settings page (3):
These paths are stored locally, which means that loading a Projucer project on different machine with a different JUCE install path should now be relatively painless as it will search for the module using the path stored locally on that machine instead of the exporter paths saved with the project. The paths can be set via the “Global Search Paths…” menu item under either “Projucer” (Mac) or “File” (Windows and Linux):
The “Add a module…” menu item in the Modules tree now displays modules found in the global JUCE modules, global user modules and exporter paths separately so it is easier to distinguish modules if you have multiple installations of JUCE:
If you have any feedback or bug reports using this new feature please post them in this thread.