-
Notifications
You must be signed in to change notification settings - Fork 386
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
[F.Rq.] Port to Windows on AArch64 (a.k.a. ARM a.k.a. WoA) #2731
Comments
edit 2021-07-16: WinForms in .NET 5 can now run natively in Windows on ARM. edit 2024-12-01: With Microsoft's push for ARM this year, I believe Win11 includes a Rosetta equivalent, so the x64 version can be used. see also #1415 |
Waterbox core support for Arm is theoretically possible, but a big ask of its own. Are we tracking that here too? |
Looking through BizHawk source, it should be theoretically possible as well. First I'm reading about MAUI though, that sounds like a more plausible refactor path, as UWP would require a compete rewrite (as far as the WinForms components) in terms of needing to start a new VS project and copy code over. |
bump for a more simple approach, you can try box64. It essentially emulates x86_64 architecture on arm. I don't think anyone tested bizhawk yet with it. |
I tested this in box64. What hasher function is being used here? |
What are you referring to? I don't see any mention of a hash function in box64's docs. |
I'm referring to this. ptitSeb/box64#506 It's on the bottom of the page. |
Oh, the
It's meant to fall back to an managed implementation if the CPU it's running on doesn't support accelerated instructions, but of course the detection code is also x86 so it can't run. You could build it for ARM, properly or with stubs, or have EmuHawk catch the lib load error and treat it as though the unmanaged call returned false. |
Does anyone know how we can use mkbundle to run bizhawk? With this, we can run bizhawk without mono installed. |
RTFM. Please only use this thread to discuss Windows AArch64 support, which with .NET Framework 4.8.1 may end up being quite simple. (future humans: go to https://github.com/dotnet/core/issues/7709 for docs.) For Linux, I won't be supporting anything other than Mono for the time being, but if anyone is having trouble with Mono on AArch64 then I'll help where I can. |
Looking over the project, a successful transition from .Net Standard 2.0 and Framework 4.8 into .Net Core 5.0 and dropping WinForms in favor of UWP would allow successful porting into WoA.
The text was updated successfully, but these errors were encountered: