An annoyance, which also leads to another problem (in a separate post)
- When I already have the JUCE source tree somewhere and disable copying, IntroJucer creates a folder called “JuceLibraryCode” which doesn’t have any actual library code, just a tree of directory stubs leading to header files consisting of one-liner #include with relative paths:
why is this necessary? I already have a nice well formed JUCE tree with full sources parallel to my application directory:
IntroJucer already knows how to set up include paths. It would be a simple matter to just add the JUCE tree location to the include paths, instead of JuceLibraryCode:
Why didn’t IntroJucer just set “…\JUCE” instead of “…\JuceLibraryCode”? It has all the information it needs. Then I don’t have a bunch of useless header files pretending to be the JUCE headers but really just one liners.