Open ajalexei opened 1 year ago
For the vast majority of cases, there's an x86 installer (which can run on x86_64 or arm64), that installer detects the "correct" architecture to install, and installs it. The only reason an x86_64 installer exists is to support versions of Windows with all 32 bit support removed (WinPE, Nano Server, etc.)
The build system produces arm64 ysetup.exe, I just haven't posted links to it because I can't find a scenario that it would help.
When can an arm64 system not run the emulated x86 installer?
The arm system can run the emulated x86 installer. However I much prefer to run the native binaries due to their lower power consumption (one of the points of the Windows arm however disputable). That is at least the case where that would help me, and maybe other Windows on arm users. Given the system produces the native arm installer anyway, is there any issue with posting the link?
The reason I'm avoiding posting links is it's simpler to have a single installer that works everywhere without users having to know which one to run. The binaries it installs will be native arm64, so the power overhead is fairly minimal. It'd be great if Windows had fat binaries, but it doesn't...
Ah, so the installer is x86, but the binaries are appropriate to the system?
That's great.
Perhaps some indication on the Yori webpage that the installer is universal might be helpful.
So far I quite often see the binaries/installers for x86 or x86_64, and if not indication assume it is x86-only.
How difficult would it be to make an arm64 installer in addition to the x86_64?
I know that the code is arm64 ready -- I used to compile the arm version myself.
Given there is a cross-compilation option for Visual Studio on the x86_64 machines, it seems relatively straightforward to produce an arm binary?