Closed rosshoyt closed 1 year ago
Hi there!
I would simply comment out the calls to code signing and notarization -- on windows that'll pop a malware warning, however on a mac that'll make life pretty frictionfull for anyone else trying to install (including yourself).
I'll publish a post soon about how to pop the mac cert in, its straightforward.
Thanks! Commenting out all the calls to code signing and notarization for Windows and Mac worked.
I then needed to update the project name in dmg.json and installer.iss to the exact same as ProjectName in CMakeLists.txt. CI Build was able to run after that!
I'd like to use the GitHub actions pipeline to build the plugin for VST/AU, and generate installers as well if possible. However I don't yet have the MacOS or Windows certificates that are used in the GitHub actions script. Do you recommend an approach for this situation, before the certificates have been obtained?
Thank you!