Add workflow to build package for windows-arm64 #1369
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since Go compiler support cross compiling, and Windows 11 on Arm support emulation of x64 apps. We can simply compile the most CPU-intensive core as native arm64, and keep the GUI as x64. That’s what Tailscale do.
Before GitHub offering Arm runners, it is an easy way to improve the performance for Windows 11 on Arm.
I had tested the windows-arm64 package on 8cx Gen3 (Matebook E Go), it was working properly.
If anyone needs windows-arm64 package, it can be downloaded from the releases. I would keep my fork merging with the main branch.