Distributing a plugin with a C++ library compiled a .dylib (apple)

Grasshopper GH for Mac
1

I’ve compiled a plugin for Grasshopper with a C++ library compiled as a .dylib.
I work on a M4 Max and it works perfectly.

I have sent the compiled files to someone else on a M2 Max (also Apple Silicon), and when they load the plugin in grasshopper it can’t read the .dylib.

First of all, is this likely to be mitigated if we disitribute over the packagemanager?

Does anyone know what the reason for this could be?
I assume it has something to do with it coming from an ‘untrusted developer’ when I compile it and send it to someone else…

2

You assume correctly so.

The right thing would be to have the dylib notarized and signed.

The quick route would be to have the user manually remove, using the terminal, the quarantine flag from the dylib after installing

4

Now the curious question - how would you solve this with the packagemanager. Would it require me to have a apple developer account (99USD pr year), or will the packagemanager take care of this?

5

It is your code, so you will have to manage that. The PackageManager doesn’t do that for you, it only helps distributing plug-ins.

6

I’m just helping getting a plugin out for Mac, that currently only exists for windows. I have managed to compile it for my own needs. I know very little about distribution of plugins etc, but I assume that even if we distribute it via packagemanager the dylib file will still be with me (who compiled it) as author, unless I get someone with a apple developer account to notarize it.>

I’ll look into this.