What do you want to change?
I’d like to add support for a Windows arm64 binary output since I use a Windows arm64 machine at work very frequently and I can’t run pi there right now without emulation.
Why?
This solves being able to run a non-emulated binary on all modern Windows architectures and simplifies installation of pi through tools like mise that default to looking for a package which matches the host architecture.
How? (optional)
I would patch the build-binaries workflow and shell script to allow for windows-arm64 as a valid platform and make sure all architecture specific dependencies (clipboard, sharp, koffi) are correctly referenced from the build-binaries shell script and that their outputs are uploaded in the workflow, also named build-binaries.
What do you want to change?
I’d like to add support for a Windows arm64 binary output since I use a Windows arm64 machine at work very frequently and I can’t run pi there right now without emulation.
Why?
This solves being able to run a non-emulated binary on all modern Windows architectures and simplifies installation of pi through tools like mise that default to looking for a package which matches the host architecture.
How? (optional)
I would patch the build-binaries workflow and shell script to allow for
windows-arm64as a valid platform and make sure all architecture specific dependencies (clipboard, sharp, koffi) are correctly referenced from the build-binaries shell script and that their outputs are uploaded in the workflow, also named build-binaries.