[L2Ork-dev] Mac M1 port?

[Albert Graef]

Hi Mikael,

Well, I guess that the main obstacle is that none of the core developers
has a Mac M1 to do the port. I know that the latest version of the source
compiles without any hitches on arm64 Linux systems, but the Mac build
probably needs to be adjusted for this architecture.

The other issue is the availability of nw.js builds for the architecture.
There are several open tickets on this:

https://github.com/LeonardLaszlo/nw.js-armv7-binaries/issues/16
https://github.com/LeonardLaszlo/nw.js-armv7-binaries/issues/42
https://github.com/nwjs/nw.js/issues/7620

The latter mentions a build of nw.js 0.50.1 for the M1, but we're currently
using 0.28.1 for most of our builds, and switching to a much later version
will likely cause regressions in the JS part of the application which would
need to be fixed first.

So there's quite a bit of work ahead of us, even if one of us can get his
hands on a Mac M1. If you are a developer and familiar with the Purr Data
sources, you can help to make it happen, though. :)

Albert


On Tue, Apr 27, 2021 at 3:03 PM Mikael Flarup Bagger <
mikael.bagger at gmail.com> wrote:

> Any news on a native build for the Mac M1? Purr Data for Intel seemingly
> runs ok translated via Rosetta 2, but sometimes crashes during startup
> _______________________________________________
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
> https://disis.music.vt.edu/listinfo/l2ork-dev



-- 
Dr. Albert Gr"af
Computer Music Research Group, JGU Mainz, Germany
Email: aggraef at gmail.com, web: https://agraef.github.io/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20210428/466e252f/attachment.html>