-
Notifications
You must be signed in to change notification settings - Fork 36
nrfutil 6 is not compatible with aarch64 #25
Comments
Can you try the change in #27 and see if that works for you? Right GitHub Actions only supports |
That seems to break the build.
Ran the
And this is basically NordicSemiconductor/pc-ble-driver-py#193 and NordicSemiconductor/pc-ble-driver-py#227. |
Seems like the only viable path would be to either run the old version under python2, or ignore that dependency and declare that some functionality will be missing, or try to automate a from-source build process (maybe inspired by NordicSemiconductor/pc-ble-driver#271 (comment)). |
I guess the solution for now would be to provide nrfutil v5 for Let's hear what @gregersrygg has to say as well, he is working on a Mac. |
I guess™️ btw. that the way forward is not a PyPi release of nrfutil for |
Closed PR #28, because nrfutil 5 does not work with Python 3. |
Disable nrfutil on arm64 (e.g. Apple M1/M2 Silicon) because it is not supported. See #25
Disable shipping |
A Docker container is very useful, not just for CI/CD, but also for quickly getting a workstation working. It's also a pure command line solution for headless VMs and systems. As another note, on Macs Rosetta provides good support for x84_64 binaries, but on aarch64 / arm64 Linux devices there isn't a good solution. There are tons of arm Chromebooks out there, and beefy workstations are coming from Ampere Computing, Nvidia, and other vendors. |
Fully agree, that it is useful beyond CI/CD. However this project is not intended for bootstrapping developer machines. For that we have nRF Connect for Desktop. |
Should be solved via the new nrfutil: 980ea41 |
Building the container on aarch64 results in nrfutil 5.2.0 being installed, which cannot run under python3 and fails.
Doing the same under amd64 results in nrfutil 6.1.7.
The text was updated successfully, but these errors were encountered: