Updated to the latest, on dev.
It looks like you are moving the VST3 SDK directories to the headless module here?
The projucer files immediately complain that they are missing a needed module (headless), and then add it for me (which is nice).
On mac, it then builds fine.
On Windows, the projucer generated VS files do not have include paths for the VST3 SDK folders in the new headless location, and so fail at VST3_Headers.h
Did I miss something simple, or is this just in progress?
Oh - even weirder - it cant find the module at all on windows.
It is definitely there, and this is the latest ProJucer (8.0.10)
Can you see that module on disk at the path specified by Path for "Visual Studio 2022"? maybe you haven’t updated that version of JUCE?
Oh yeah, it’s there alright.
Anyway, I switched back to the master branch now, since that is working for me.
Current dev head is less than a day old, I suspect there is some simple thing that just needs to get fixed by the JUCE team, and will probably be fixed quickly.
I’m not able to reproduce either the issue where you can’t find the module or the issue where the headers aren’t found. Could you share an example project demonstrating the issue please?
hmmm, I’ll take another look monday, can’t today.
I tried removing the module and readding it, and found it very strange that it had that module listed on the “add new module” popup menu, but then it was greyed out and said it couldn’t find it after it was added.
Kinda seemed like a projucer issue.
Are you absolutely certain that you’re running a Projucer built from the develop branch, and not the master branch?
Pretty sure, but easy enough to rebuild and check.
Just wondering, why would that matter though?
What does the ProJucer do differently from one to the other branch?
We make breaking changes to how the Projucer interacts with the rest of the framework all the time.
In this specific case the master branch Projucer is unaware of the new module on the develop branch.
It really is essential that you use a Projucer compiled from exact commit of JUCE you are using.
That makes sense.
I’ll swing back and double check soon, but presumably this is the issue.
Thanks!
