Feature and motivation
This is a subset of #11357. Regardless of what all we decide to support eventually, I think supporting M1/M2 is the most important piece.
Chrome, Edge & Firefox all have drivers available for it:
I'm guessing rust would put these in mac_arm64 directory instead of mac64?
Java can get the architecture from System.getProperty("os.arch"), Ruby is RbConfig::CONFIG['host_cpu'], .NET has RuntimeInformation.OSArchitecture. We'd need to get it all tested somehow.
The compiling/cross-compiling piece I don't think should be a limiting factor. Someone with an M1 can build the binary and we package it like the others.
Usage example
n/a
Feature and motivation
This is a subset of #11357. Regardless of what all we decide to support eventually, I think supporting M1/M2 is the most important piece.
Chrome, Edge & Firefox all have drivers available for it:
I'm guessing rust would put these in
mac_arm64directory instead ofmac64?Java can get the architecture from
System.getProperty("os.arch"), Ruby isRbConfig::CONFIG['host_cpu'], .NET hasRuntimeInformation.OSArchitecture. We'd need to get it all tested somehow.The compiling/cross-compiling piece I don't think should be a limiting factor. Someone with an M1 can build the binary and we package it like the others.
Usage example
n/a