Modules with ARM builds!

If any of you are running the arm free beta, there was a great change in the 222 sdk which I think is awesome - I was a big advocate for the change! - but which means the 222 sdk makes an arm plugin with different names than 221.

So short version: if you use the surge arm beta it now uses the 222 sdk and so you need 222 free

And plugins built with 221 that haven’t updated yet may not load properly. If they don’t just rename plugin.Dylib to plugin-arm64.dylib

(This change means you can have a rack user directory with both arm and x64 plugins in one spot which is super operationally useful and I’m thankful for vortico and team for adding it)

3 Likes

question related to this, is there a reason to simply not have universal builds?

with the sdk using makefiles the build would only need a few extra flags to support it…

3 Likes

If i helps anyone, I wrote a little script to build and push module sets on GitHub into my rack dir on my mac so I can get enough to do my dev and test work. Nothing special but figured I’d share while we are in the interim before arm library.

2 Likes

Hi everyone, just a heads up: AS free plugin (and both paid ones) are running fine on Mac Rack 2.2.2 free ARM

I guess the users with the paid plugins have to wait until an official Rack ARM release is available?

4 Likes

https://drive.google.com/drive/folders/11k81iJwAW_xP3fNGO9ZmNh-XwS2DexbF

1 Like

are those all being distributed in accordance with their licenses? GPL-3 has a lot to say about distributing binaries.

If you read the README-LINUX-CHROMEBOOK-armv8-a-BUILDS.md it explains how to obtain the source, or more exactly how the source was obtained.

2 Likes

ah, yes. tx.