Sharing patch with externals on MacOS

Hi list,

in case there is anyone using mac systems: I have a patch that I usually 
distribute together with Pd and the external libraries fd_lib, zexy, 
midifile and iem_tab. Recently while helping someone setting it up, I 
noticed that because none of this software is authorized (?), on modern 
OSs it's necessary to allow the system to use each of these libraries 
separately, by accepting each one in the system security settings, 
restart Pd, repeat several times, until it will eventually work. And if 
an update happens, the same process will have to be done again. From 
what I remember from the past, it seems to have become worse in the last 
years.

This patch is distributed to "normal computer users", which makes it a 
very big hurdle to make it work, as most of them don't even know that 
there is an error, how to correct it, etc. They will just assume that 
something doesn't work, and don't use it.

Are there any ways to avoid this from happening, so that running the 
patch would be just as simple as double-click on the file?


I'm also not a certified member-paying mac developer, but seemed to have 
managed to authorize my own patch/standalone, so that it can run. Any 
helpful tips on dealing with that?


(extra details for context:

- this happens with the Pd patch, and also with the same patch 
encapsulated in a Max-Msp patch and standalone, running with pd~

- while trying this out, we managed to get the patch running. but when 
the files were moved to a different folder, it stopped running, and 
there were no system warnings that something was blocked. after moving 
the files to the previous folder, it worked again)


Best,

Joao

---
[email protected] - the Pure Data mailinglist
https://lists.iem.at/hyperkitty/list/[email protected]/message/KLDMOQUZCUNROWT5KFKSYVDTQRFEFHBL/

To unsubscribe send an email to [email protected] mailing list
UNSUBSCRIBE and account-management -> https://lists.iem.at/