Embedded Frameworks: Multiple commands produce framework

[reuk]

@dbpsch

I tried pointing the Embedded Frameworks directly to the custom.xcframework/macos-arm64_x86_64/custom.framework. This let me build AU and standalone but VST3 still fails because of the VST3-Manifest Helper (with basically the same error, but coming from a copy command and can be solved the same way by selecting copy only on install).

You say that the AU and Standalone builds succeed, but do they run? Can you load the resulting AU in a DAW, or launch the Standalone? If the AU and Standalone don’t work, this might indicate that the framework dependency isn’t being resolved correctly. The VST3 build failure would be caused by the juce_vst3_helper failing to load the plugin bundle.

Framework dependencies are discussed here:

Ableton Live 11 fails to resolve rpath of dylib in VST3 plug-in, but other DAWs work

Thanks for the reply. I’m not using cmake, but I can discern the steps from the code you shared. I might not have been clear in my previous post, but I’ve essentially done the steps you’ve outlined manually: copying the dylib into the VST3 bundle in a Frameworks directory using installl_name_tool to change the relative path to the @loader_path path within the bundle on the VST3 binary in the MacOS directory verifying the library path change using otool -L and otool -L on the VST3 binary Howe…

You could try adding the rpath flag to the extra linker flags, as mentioned in the final post. This might allow the system to find the framework dependency.