I upgraded to JUCE 7.0.10 today and I’m having problems building for VST3 on MacOS with XCode. I wasn’t sure if there’s something unusual in my project (I’m working through the synth project from the “Creating Synthesizer Plug-Ins with C++ and JUCE” book), so I tried making a fresh plugin project with Projucer and it seems like there is a consistent new problem in 7.0.10.
I downgraded to 7.0.9 to double check and it’s still fine there: I can create a new plugin project in Projucer with the default options. I export to XCode, build the VST3 target, and it succeeds. I can open the plugin in the AudioPluginHost and it works as expected.
Now I try the same thing after upgrading to 7.0.10. When I try to build in XCode I get this error and the build fails:
juce_VST3ManifestHelper.mm Build input file cannot be found: '/Users/.../path/to/my/project/Builds/MacOSX/~/JUCE/modules/juce_audio_plugin_client/VST3/juce_VST3ManifestHelper.mm'. Did you forget to declare this file as an output of a script phase or custom build rule which produces it?
The interesting thing is ~/JUCE/modules/juce_audio_plugin_client/VST3/juce_VST3ManifestHelper.mm
exists. So maybe it shouldn’t be pre-pending the path of my project to this module path?
Is this a new bug in the XCode exporter? Any workarounds? I’m learning JUCE and C++ and XCode pretty much all at the same time, so I’m completely lost as to why this is happening or what to do about it. So I’ll keep using JUCE 7.0.9 for now.
More details:
- I am putting the currently installed JUCE at the path ~/JUCE, which I think is the standard location on MacOS
- I’m on MacOS Ventura 13.6.3 running XCode 15.2
- This forum post might be related: Xcode recovered references juce_VST3ManifestHelper.mm