Building on Apple Silicon (M1) Macs

If the native extensions are built for one version of Ruby, but the app loads by running a different version of Ruby, maybe that’s a problem?

Ok, this sounds like fairly reasonable behaviour. Very glad to see that all the other processes shut down on their own, that’s the new daemon zombie killer script in fully gory action!

I think the issue you’re seeing is with the GUI in M1 compatible mode. It may possibly be due to boost issues with a non-M1-native SuperCollider - it might be a Qt issue or something else, but at least we’re getting closer!

1 Like

Good call, but it’s unlikely an issue now we’re not really using any native extensions in Ruby except for the Rugged stuff which is non-essential at this stage.

1 Like

Sorry to report lack of progress; haven’t had much time to work on this. The idea to use the Python script aqt to semi-automatically pull Qt 5/6 failed on both Mac and Raspbian, because the ARM architecture version is not there.

1 Like