# New and existing VST3 projects won't build on MacOS after upgrading to JUCE 7.0.10 **URL:** \ **Category:** MacOSX and iOS\ **Created:** [February 14, 2024, 3:03am UTC](https://forum.juce.com/t/new-and-existing-vst3-projects-wont-build-on-macos-after-upgrading-to-juce-7-0-10/59969 "2024-02-14T03:03:55Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![adamjmurray](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/adamjmurray/32/17875_2.png) [@adamjmurray](https://forum.juce.com/u/adamjmurray)\ **Post date:** [February 14, 2024, 3:03am UTC](https://forum.juce.com/t/new-and-existing-vst3-projects-wont-build-on-macos-after-upgrading-to-juce-7-0-10/59969/1 "2024-02-14T03:03:55Z")
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](https://forum.juce.com/t/xcode-recovered-references-juce-vst3manifesthelper-mm/59565) ---
**Author:** ![t0m](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/t0m/32/16413_2.png) [@t0m](https://forum.juce.com/u/t0m)\ **Post date:** [February 14, 2024, 2:42pm UTC](https://forum.juce.com/t/new-and-existing-vst3-projects-wont-build-on-macos-after-upgrading-to-juce-7-0-10/59969/2 "2024-02-14T14:42:38Z")
There’s a fix on the way. ---
**Author:** ![barelyosi](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/barelyosi/32/17058_2.png) [@barelyosi](https://forum.juce.com/u/barelyosi)\ **Post date:** [February 14, 2024, 11:18pm UTC](https://forum.juce.com/t/new-and-existing-vst3-projects-wont-build-on-macos-after-upgrading-to-juce-7-0-10/59969/3 "2024-02-14T23:18:56Z")
From editor tab Build Phases → Compile Sources “TARGETS” → “{YOUR\_PROJECT} - VST3 Manifest Helper” copy the Compiler Flags In File navigator remove (REFERNCE no Move) the juce\_VST3ManifestHelper.mm from “Recovered References” group. (Remove Reference). Right click on “Recovered References” choose “Add file to YOUR\_PROJECT” navigate to “JUCE/modules/juce\_audio\_plugin\_client/VST3/” and add “juce\_VST3ManifestHelper.mm” Click on your root project from file navigator, in editor tab click on “Target {YOUR\_PROJECT} - VST3 Manifest Helper” (from where u copied the Compiler Flags, now is without Compile Sources) Build Phases → Compile Sources click + and navigate to “Recovered References/juce\_VST3ManifestHelper.mm” and add the file In “Compiler Flags” past the copied flags ---
**Author:** ![t0m](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/t0m/32/16413_2.png) [@t0m](https://forum.juce.com/u/t0m)\ **Post date:** [February 15, 2024, 9:04am UTC](https://forum.juce.com/t/new-and-existing-vst3-projects-wont-build-on-macos-after-upgrading-to-juce-7-0-10/59969/4 "2024-02-15T09:04:41Z")
> ---
**Author:** ![adamjmurray](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/adamjmurray/32/17875_2.png) [@adamjmurray](https://forum.juce.com/u/adamjmurray)\ **Post date:** [February 15, 2024, 5:20pm UTC](https://forum.juce.com/t/new-and-existing-vst3-projects-wont-build-on-macos-after-upgrading-to-juce-7-0-10/59969/5 "2024-02-15T17:20:56Z")
Ok cool, so it looks like if I build JUCE myself from the develop branch, this will be fixed. I assume this fix will be in the 7.0.11 release if I wait for that? Also, thank you @barelyosi for the workaround info. Since a proper fix is now available I will rely on that. ---
**Author:** ![3-aln](https://avatars.discourse-cdn.com/v4/letter/3/4da419/32.png) [@3-aln](https://forum.juce.com/u/3-aln)\ **Post date:** [February 18, 2024, 9:37pm UTC](https://forum.juce.com/t/new-and-existing-vst3-projects-wont-build-on-macos-after-upgrading-to-juce-7-0-10/59969/6 "2024-02-18T21:37:22Z")
Just wanted to say thanks for posting this and for the solutions shared! Was in the exact same boat and would have been left scratching my head if not for this thread. 😄 ---
**Author:** ![adamjmurray](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/adamjmurray/32/17875_2.png) [@adamjmurray](https://forum.juce.com/u/adamjmurray)\ **Post date:** [March 19, 2024, 4:55am UTC](https://forum.juce.com/t/new-and-existing-vst3-projects-wont-build-on-macos-after-upgrading-to-juce-7-0-10/59969/7 "2024-03-19T04:55:50Z")
If you installed 7.0.10 on a Mac, a simple workaround is to edit global paths in Projucer and change `~/JUCE` to the corresponding absolute path (like `/Users/adam/JUCE`), and also change the JUCE modules path to be an absolute path.