Ok cool. So the workaround is ok and can be added to the .app bundle build stage.

As for the initial app warning, as far as I can tell, the only way to remove it is to sign the app with a developer ID. This requires an account and $100 a year.

enohp ym morf tnes
-----------
Dan Wilcox
danomatika.com
robotcowboy.com


On Dec 12, 2019, at 6:24 PM, Kevin Haywood <khaywood@ucsd.edu> wrote:

That appears to work!

I opened patches with a couple of older dsp externals that I hadn’t validated yesterday, and they all ran fine. Only got this message upon launch of your app, which I guess is just the Catalina version of this old message, since it could be bypassed as before by launching the app with a right-click and choosing “Open”:

“Pd-0.50-2-signed” can’t be opened because Apple cannot check it for malicious software.
This software needs to be updated. Contact the developer for more information.

Kevin


On Dec 12, 2019, at 2:58 AM, Dan Wilcox <danomatika@gmail.com> wrote:

Looks like the solution (as listed at https://cutecoder.org/programming/shared-framework-hardened-runtime/) is either:

1. sign the Pd app and disable plugin validation; or
2. use externals built for a min version of macOS 10.9

I've tried option 1 by "ad-goc" signing Millers Pd 0.50-2 build with the library validation entitlement disabled:


Please test.

On Dec 11, 2019, at 11:23 PM, Dan Wilcox <danomatika@gmail.com> wrote:

We might need to add an entitlements file which specifies which things are "allowed," one of which is loading non-signed external libs. I ran into this with a project at work which uses libpd and loads a couple externals.

On Dec 11, 2019, at 9:56 PM, Kevin Haywood <khaywood@ucsd.edu> wrote:

I just discovered the huge headache of the notarization system under Catalina: the OS will prevent loading of every non-notarized *external* that you try to load. ...