On 02.09.2024 at 10:47, Jordi Boggiano wrote: > On 28.08.2024 21:16, Christoph M. Becker wrote: >> (1) The libraries on which several extensions rely are not yet available >> for Windows on arm64; at least the winlib-builder[2] would need to be >> improved in this regard, but of course, some libraries may not even >> support Windows on arm64 yet. >> >> (2) To my knowledge, none of the core developers has a Windows on arm64 >> environment available, and I presume that nobody wants to run an arm64 >> emulator on an x64 machine. And since there are no public GH runners >> for that platform (that might change in a couple of months, though[3]), >> we cannot actually test (let alone develop) these builds. > > I don't have much knowledge about the compiler aspects but to your point > 1 from what I understand (as a user of a Surface Pro 11) some apps are > built for ARM64 but with some x64 compatibility in mind, that's referred > to as ARM64EChttps://learn.microsoft.com/en-us/windows/arm/arm64ec - > I've seen this done for Microsoft Office which needs to support some > legacy x64 plugins and also foobar2000 to support x64 plugins that are > abandoned and won't be recompiled any time soon. I'm thinking this might > help with lib dependencies here?
Generally, doing ARM64EC builds might make sense, but since these require Windows 11, we have the same issue regarding Github, where currently available windows-2022 runners run on Windows 10. > As for 2, I kinda need my computer still but I can offer to test run > some builds if it helps. Thank you, that would be very welcome, if we decide to ship builds for Windows on arm64. That decision is, of course, not up to me. Christoph
