The EAR Production Suite is a set of VST® plugins and tools for producing immersive and personalizable audio content suitable for any Next Generation Audio codec. It is based on the Audio Definition Model (ITU-R BS.2076) and the ITU ADM Renderer (ITU-R BS.2127) and enables monitoring on any ITU-R BS.2051 loudspeaker configuration.
Some mac machines seem to use translocation on the setup application bundle even though the application and the disk image itself is signed. This is not expected behaviour going by Apple Developer documentation - a signed and notorised disk image containing signed binaries should not need any translocation. When translocation happens, the setup application can not locate the setup files as the application has been moved to a random directory. Perhaps a bug? Only seems to affect the odd machine.
In any case, we need a workaround. This fix places all of the setup files in the Resources folder of the setup application. This way, even if translocation occurs, setup still has access to all of the setup files it needs.
If NOT running on CI, CMake will copy resources in to setup bundle as post build step - this allows for local testing.
If running on CI, the resources will be copied in to the bundle as part of packaging by setting the install directory for the other targets to Setup EAR Production Suite.app/Contents/Resources
Other bits to support it;
CMake scripts keep track of all of the EPS VST targets as they're added. This is pushed up to root scope (hence lots of PARENT_SCOPEsets to push it up through the chain.) Less chance of forgetting any new plugin during copy stage this way.
Setup application code changed to look within own Resources folder for plugins/extension/templates/tools etc when installing
CMake version parsing code updated to not look for a hyphen separator for final section of a version. This allows us to have "1.1.0b".
Updated changelog for the "b" release
Added setup icon (otherwise macos seems to just choose a random thing from inside it's Resources folder)
Some mac machines seem to use translocation on the setup application bundle even though the application and the disk image itself is signed. This is not expected behaviour going by Apple Developer documentation - a signed and notorised disk image containing signed binaries should not need any translocation. When translocation happens, the setup application can not locate the setup files as the application has been moved to a random directory. Perhaps a bug? Only seems to affect the odd machine.
In any case, we need a workaround. This fix places all of the setup files in the Resources folder of the setup application. This way, even if translocation occurs, setup still has access to all of the setup files it needs.
Setup EAR Production Suite.app/Contents/ResourcesOther bits to support it;
PARENT_SCOPEsets to push it up through the chain.) Less chance of forgetting any new plugin during copy stage this way.