WIP: Arm support for Node

[birkskyum]

No description provided.

[birkskyum]

@jutaz , this is the problem at hand.

[jutaz]

Cool, I’ll take a look over the weekend, hopefully 👍

[acalcutt]

I think arm was pretty much working in #459

i doesn't run in every version of node like the current workflow, so i doesn't have the node 14 issue.

[birkskyum]

My understanding of the problem is that it is possible to manually activate Rosetta 2 on the machine with arch -x86_64 zsh, then run nvm install 14 to install node with Rosetta 2, and that's it. It just doesn't work with the setup-node action. Basically this

[acalcutt]

i could update to use 'macos-12-arm' and remove node 10 there.

[birkskyum]

@acalcutt , that would be great!

[acalcutt]

One positive is the workflow is less 'heavy'. It only runs on one node version per os instead of 3 node versions. It use the fact that one build makes multiple node abi versions, so it won't need to run on node 14 arm can't build on.

Downside

• when using node-pre-gyp with the --target , it uses a abi_crosswalk.json file that is out of date. I had to make my own version of the package to support node 18. We may be able to change back to the officially one if they add node 18 support.
• It is not tested for every node version, just the node version it builds on.

[birkskyum]

Is it possible for an m1 runner to make builds of 16 and 18 that can be used on x86 macs as well?

[acalcutt]

I tried to make a universal build like you suggested here https://stackoverflow.com/questions/65157483/macos-build-universal-binary-2-with-cmake, with "CMAKE_OSX_ARCHITECTURES=arm64;x86_64" but it was always missing compenents from the architecture it wasn't running on.

[acalcutt]

FYI, I think I found that command needed quotes like

-DCMAKE_OSX_ARCHITECTURES="arm64;x86_64"