Translocation fix

[firthm01]

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_SCOPE sets 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)
• Codesigning script updated

[rsjbailey]

Looks good, just a question about the installation destination stuff when packaging & a couple of small tweaks

[rsjbailey]

I think this is only true when run on CI? (took me a while to track it down, but I think '.' means the root of CMAKE_INSTALL_PREFIX, which is set by build.yml)
If we were to configure and install locally with EPS_PACKAGE set, does that mean we'd get everything in the CMAKE_INSTALL_PREFIX root, (and presumably the setup app would be broken?)

Is there a reason for doing it that way, or would we be better with

install(FILES
        README.pdf
        LICENSE.pdf
        DESTINATION
# note still starts with a '.' otherwise cmake will assume
# generator expression resolves to an absolute path
# also might need to escape the spaces
# also might be broken, I'm just thinking out loud :)
        .$<$<PLATFORM_ID:DARWIN>:/Setup EAR Production Suite.app/Contents/Resources>

# other install commands 

and keeping the install prefix consistent?

[rsjbailey]

Oh wait, I just saw your comment at the top of the PR. Sorry :)

[rsjbailey]

I guess it's maybe still valid as it's nice to be able to do a CI-style build locally (I don't think doing it this way negates that as the packaging file is only run if specified via a cache var). If it's hard for some reason (the post-build step suggests it probably is) then maybe keep things as they are.

[firthm01]

Issue #275 opened to tackle local packaging at a later date