Added support for Windows on ARM64. #3112
Conversation
azchohfi
force-pushed
the
winArm64
branch
4 times, most recently
from
2c8b79a
to
d7f6d7d
Compare
|
I'm setting up my Surface Pro X to build everything in it, then run the functional test on real ARM64 hardware. |
|
All test passed! \o/
|
|
How is this working without moving to .NET 5? I don't see Win/X64 on the support list for .NET 3.1. |
|
I don't think its officially supported, so its probably one of those features that are in unsupported preview. We should, ideally, move to .NET5 before merging this, but I moved it locally to .NET5 RC1 and it also worked, exactly the same. Both versions were not running as emulated x86. They were native 64 bit(ARM) processes. |
|
Thanks @azchohfi!! Hope this will bring us a bit closer to getting hosted Windows ARM64 agents in Azure Pipelines, to push things like NodeJS Windows arm64 support forward 🚀 |
|
@dennisameling what would you do with a Windows ARM64 agent that you can't do today? From that linked issue it seems things are working fine using the x86 agent. Also to be super clear: this PR is unrelated to whether we offer hosted ARM64 machines. A lot of things have to fall into place for that (Azure to offer hardware + our friends over at https://github.com/actions/virtual-environments to offer images + a business case for the cost of such pools). At the moment, I don't plan to merge this PR. |
|
@vtbassmatt You're right. Yes, things are working with the x86 agent. I was just hoping that this was some minor step in the direction of hosted ARM64 machines. I know this PR is not directly related to that. Fingers crossed for some hosted ARM64 pools to become available soon 🤞 then those will be able to run the x86 agent as well, like you mentioned. 👍 |
|
Glad to know you aren't blocked. And I forgot to say thanks for the data point you provided about projects building for Win/ARM64 - I wasn't aware Node was doing so, and it's one of our agent dependencies 😁 |
|
Is there anything known blocking this? |
#2062