@piotr I shall admit I'm a bit confused by the fork way of working and the wine CI.
I previously made some rebase, but now, when I click on the rebase button, nothing happens.
I didn't want to bother you before the windows build pipelines were successful, but your offer is welcomed.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/7109#note_93055
The patches needs to be rebased on top of current master. You will also need to merge the patches/reverts and get rid of the merges. I have requested access to your repository if you need help with that.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/7109#note_93054
On Mon Jan 27 21:05:00 2025 +0000, Alexandre Julliard wrote:
> Actually _Cbuild has the same problem, but it's less obvious since it
> will break only on non-x86 platforms.
Hello. Thanks for the clarification!
=> Change of Cbuild then.
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/7109#note_93053
This allows using one single wineprefix, one wineserver and one single wine executable for running both arm and arm64 executables.
This setup actually has worked earlier; Ubuntu 22.04 packages Wine 6.0, where the wine32 + wine64 packages together end up working this way. However, since Wine 6.0, a couple of refactorings has broken this setup along the way; reinstate this way of working.
The new wow64 mode probably won't work on arm, as it's not easily possible to switch between 32 and 64 bit execution mode within a process, as far as I know, but the old wow64 mode is still a great convenience - especially considering distro-packaged use for users who aren't familiar with the particular quirks on this architecture.
--
v2: configure: Allow using --enable-win64 on aarch64
server: Include ARMNT as one of the supported architectures on aarch64
ntdll: Allow running arm/aarch64 in (old) wow64 mode
https://gitlab.winehq.org/wine/wine/-/merge_requests/7204