-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Windows ARM64 #13331
Comments
This would suffer from the same cross-compilation issues that Linux does [1]. Since Microsoft don't license ARM64 Windows I doubt that there'll be support for compiling in CI via a VM. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
I started looking into this, and I've discovered there are other bugs that need to be fixed before we can get Deno to build. Ring isn't working right now |
I've got a working, temporary solution to build against a patched ring 0.16.20 release for Windows ARM64, see instructions here if it can help: briansmith/ring#1514 (comment) |
There's now a new ring release, I'm gonna try to find some time to try this again by upgrading to the new Ring release. |
Supporting Windows on ARM natively is table stakes, my expectation is that I can use |
@gamedevsam I'm looking for the same, as more business and consumer computers are moving towards ARM architecture. I can see Deno supports Mac and Linux on ARM though. I believe an older 1.x version of Deno supported Windows on ARM? |
I've been using a Surface Pro X as a main machine and I'm interested in using Deno on it.
So far, I've been using the Linux/ARM64 builds made by @LukeChannings, https://github.com/LukeChannings/deno-arm64, they work well in WSL2.
It would be even nicer to use if I can run it natively in Windows instead.
I found this blog post about supporting Windows ARM64: https://patriksvensson.se/2020/05/targeting-arm-for-windows-in-rust/
The text was updated successfully, but these errors were encountered: