Projucer with current Master Branch deletes Plugin binaries at the custom shell script stage

[Dave_Chambers]

I’m building a synth and have not had the chance to work on it for several months. Today I checked out Master branch, complied the Projucer and attempted to build my project in Xcode.

The JuceDemoPlugin works fine but for my project, the AU, VST3 and VST binaries are created and then deleted after the linking phase has begun, when the custom shell scripts are run, resulting in the following errors:

Copying to VST3 folder…
cp: /Users/davechambers/Documents/Dev/Zeus/Builds/MacOSX/build/Debug/Zeus.vst3: No such file or directory
sed: /Users/davechambers/Library/Audio/Plug-Ins/VST3/Zeus.vst3/Contents/PkgInfo: No such file or directory
sed: /Users/davechambers/Library/Audio/Plug-Ins/VST3/Zeus.vst3/Contents/Info-VST3.plist: No such file or directory
Command /bin/sh emitted errors but did not return a nonzero exit code to indicate failure

Previously I had checked out the code from December 1st 2015 and was using the Introjucer (this combination still works)

I’ve made a video of the process here:

https://www.youtube.com/watch?v=D1O4o9m3OUY&feature=youtu.be

Any help would be great

Dave

[daniel]

Just remove the post build step. The new static library approach put’s everything at it’s place, see here:

Projucer, AudioPlugin project: XCode post build script called more than once

This is due to the Projucer creating now various targets under XCode, and the post build script being invoked once per target (e.g. “Shared Code” and “VST”). This causes the copied VST to be copied during the first call / target, and then deleted in the following one. Quick-fix: deleting manually all but the “Shared Code” post build step script. Cheers

And there (especially the screenshot there):

[fixed] AAX plugins created with 4.2 no longer loadable in ProTools development build

I have now implemented this, please update to the newest tip! You will find these new Projucer build settings. Grey means it’s using the default setting - you can however override it per configuration (debug/release). [image] Enjoy. Hope this makes working wth JUCE 4.2 easier.

EDIT: and the actual issue:

[fixed] Set CONFIGURATION_BUILD_DIR for Xcode projects

I want to be able to set CONFIGURATION_BUILD_DIR aka "Per-configuration Build Products Path" for Xcode projects from Introjucer.  I've tried Preprocesser definitions, linker and compiler settings but none of those seemed to work - and when I try setting it in "Custom Xcode flags" the project becomes invalid and doesn't load. 

[Dave_Chambers]

Thanks Daniel. That fixed things