Signing doesn't happen automatically in the build system - our releases are
signed manually by the release manager. All CI builds are unsigned.
There might be some ad-hoc signing done by XCode 11+. Maybe you could
try changing
CI
<https://github.com/supercollider/supercollider/blob/develop/.github/workflows/actions.yml#L201>
to build with XCode 10.3? I don't know if this makes a difference but maybe
it's worth a try. Also, we now added legacy build to GHA that builds with
XCode 10.3 already.
On Wed, Mar 10, 2021 at 1:55 PM <[email protected]> wrote:
> Hello Marcin,
>
> I tried with the built from the actions tab but the issue persists. I
> don’t really understand the process but I assume the signing happens in the
> build automatically.
> Is there another way to obtain the unsigned built? I assume I only need
> the plugins folder… 🤔
>
> Best,
>
> Dionysis
>
> On 10 Mar 2021, at 20:47, [email protected] wrote:
>
> Hi Dionysis,
>
> I have a rather vague understanding of this, but I'd suggest trying with
> an unsigned build. I think manipulating signed builds is not likely to work
> - but I might be wrong. Unsigned builds do work on Catalina/Big Sur, but
> they give a scary warning and you need to right-click->open them twice.
> After that, they work fine (including microphone input permissinos, which
> has been fixed somewhat recently).
>
> The easiest way to get an unsigned build would be to probably use the
> current develop build. Also, now that we've switched to GitHub Actions, you
> can relatively easily trigger a new build in the CI on your own fork. I'm
> not sure if that would work on the regular 3.11 branch, but the
> "3.11.2-bigsur" branch should trigger the GHA build. You can then download
> the build directly from the Actions page.
>
> Again, my understanding of signing etc is vague, I hope I'm not misleading
> you :)
> Marcin
>
> On Wed, Mar 10, 2021 at 3:38 AM <[email protected]> wrote:
>
>> Hello,
>>
>> I am trying to update sc-osx-standalone
>> <https://github.com/dathinaios/sc_osx_standalone> to use 3.11 and
>> hopefully work on Catalina/Big Sur but a series of errors with the
>> following form are thrown on startup:
>>
>> *** ERROR: dlopen './Resources/plugins/GendynUGens_supernova.scx' err 'dlopen(./Resources/plugins/GendynUGens_supernova.scx, 2): no suitable image found. Did find:
>> file system relative paths not allowed in hardened programs'
>> *** ERROR: dlopen './Resources/plugins/UIUGens.scx' err 'dlopen(./Resources/plugins/UIUGens.scx, 2): no suitable image found. Did find:
>> file system relative paths not allowed in hardened programs'
>> etc....
>>
>> So it appears that plugins are not loading correctly. As far as I can
>> tell this has something to do with MacOS sandboxing but I am really not
>> sure. Does anyone have any pointers on how to resolve such an issue?
>>
>> Best Wishes,
>>
>> Dionysis
>>
>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.