I just updated my local copy of JUCE to the latest on develop and now I’m getting an error that it can’t find AAX_Version.h. What’s interesting is that I definitely have my AAX global path set in Projucer and for whatever reason, my Xcode project doesn’t show the AAX path in Header Search Paths.
Did anything change here?
Maybe Avid is getting back at me for the developer feedback I sent in…
I had this working with a relative path, however, I am no longer able to achieve this. Strangely it builds on my developer account (same repo, no global path in Projucer), but it doesn’t on Jenkins.
Thanks @ed95,
yes, I am setting it in the XCode exporter. I had to track down a soliciting Projucer from a different submodule (pluginval). But now the red is gone, it shows it as valid.
I also deleted the workspace of Jenkins, so no old Projucer can get in the way…
Unfortunately still with the same result, in jenkins it doesn’t find the includes.
My setup pulls a new JUCE repo each time and builds Projucer from scratch. The juce submodule was updated today.
Maybe worth noting: OSX 10.12 Sierra with case sensitive file system…?
(I should probably update, but I am undecided, if High Sierra or directly to Mojave)
I think I have a lead now. I just checked the paths in the console, and it used the default path from Projucer (maybe an artefact of the one, that printed the version in red).
I logged in the jenkins account and removed all paths (they appeared now thanks to the latest Projucer indeed as set, but with the invalid default value).
Now I am verifying, that my branch references the right commit (and has the AAX in the exporter, currently it doesn’t seem to be the case).
Seems here was a spring clean overdue with several issues… I think the next attempt should bring relief…
To make sure that no paths sneak into any builds, you might want to remove the global settings file each time you do a build. We have this line at the top of the CI script which builds the Projucer:
That’s a great idea… I am a bit weary of scripts, that delete files outside it’s container though…
A command line option to ignore any global settings (or even specify a separate settings file) would be a better addition for that instead.
The build succeeded now, I didn’t push the mono-repo, only the submodule, so that last bit was owed to my own stupidity
Thanks for helping out!
BTW. when you update the Projucer project files the next time, could you see, if this warning can be silenced:
warning: unknown warning option '-Wzero-as-null-pointer-constant'; did you mean '-Wint-to-void-pointer-cast'? [-Wunknown-warning-option]
1 warning generated.
OK bizarrely, I used AAX 2.4.1 instead and the problem went away. I’m guessing I had already compiled to 2.4.1 on another project, and was setting the global path to 2.4.0 which was wrong.