-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[mono][workload] Add workloads for win-arm64 using emulation #65089
Conversation
We should do the same for android and iOS |
done, I added a win-arm64 alias everywhere we had a win-x64 alias |
@@ -166,6 +166,7 @@ | |||
"version": "${PackageVersion}", | |||
"alias-to": { | |||
"win-x64": "Microsoft.NETCore.App.Runtime.AOT.win-x64.Cross.android-x86", | |||
"win-arm64": "Microsoft.NETCore.App.Runtime.AOT.win-x64.Cross.android-x86", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Redth when you're testing win-arm64, can you validate if this .exe
runs:
> "C:\Program Files\dotnet\packs\Microsoft.NETCore.App.Runtime.AOT.win-x64.Cross.android-x86\6.0.2-mauipre.1.22074.5\tools\mono-aot-cross.exe"
If it prints help output, I think that means it would work.
Draft Pull Request was automatically closed for inactivity. Please let us know if you'd like to reopen it. |
…65089) * Add wasm workload for win-arm64 using emulation * Add aliases for win-arm64 to all the win-x64 cases as well (android, ios)
…otnet#65089)" (dotnet#67154) This reverts commit 4e7ccfa.
This pairs with dotnet/emsdk#109 and would be a workaround until we have native builds of the tooling. I don't have a way to test this so we'll need some manual checks to verify.