Package Details: wine-wow64 10.4-1

Git Clone URL: https://aur.archlinux.org/wine-wow64.git (read-only, click to copy)
Package Base: wine-wow64
Description: A compatibility layer for running Windows programs
Upstream URL: https://www.winehq.org
Keywords: wine winehq wow64 x64
Licenses: LGPL-2.1-or-later
Conflicts: wine
Provides: wine
Submitter: tiziodcaio
Maintainer: tiziodcaio (xiota)
Last Packager: xiota
Votes: 41
Popularity: 2.11
First Submitted: 2023-05-06 18:16 (UTC)
Last Updated: 2025-03-22 10:41 (UTC)

Pinned Comments

xiota commented on 2024-05-22 12:10 (UTC) (edited on 2024-05-23 05:13 (UTC) by xiota)

This package is still relevant because multilib/wine does not have wow64 mode enabled and/or has not dropped lib32 depends.

Hanabishi commented on 2024-05-22 11:55 (UTC) (edited on 2024-05-22 12:01 (UTC) by Hanabishi)

@dreieck, https://gitlab.winehq.org/wine/wine/-/releases/wine-9.0#wow64

TLDR: with new WoW64 mode, you can run 32-bit Windows apps on pure 64-bit Linux system, i.e. without multilib/lib32-* dependencies installed.

tiziodcaio commented on 2023-09-11 14:58 (UTC)

Added wine-staging-wow64, the wine-wow64 package with staging patches!

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »

yan12125 commented on 2024-02-24 04:37 (UTC)

On my machine, samba also brings smbclient. Those extra dependencies use 20% extra space compared to wine-wow64 (just ignore the giant multilib/wine).

Not a big deal, anyway.

yan12125 commented on 2024-02-21 05:37 (UTC)

Hi, I noticed that some heavy dependencies, like samba and sane, are moved from optdepends to depends in 9.0rc3 [1]. Are they necessary? Maybe it's better to roughly follow dependencies of multilib/wine package, with lib32-* ones excluded.

[1] https://aur.archlinux.org/cgit/aur.git/commit/?h=wine-wow64&id=43e585e4f0d5858d4277d85b20a14f595959919a

xiota commented on 2024-01-20 13:52 (UTC) (edited on 2024-01-20 13:56 (UTC) by xiota)

@tiziodcaio The variables make common details between packages easier to keep in sync. It's fine if you prefer not to use them.

When --with-wayland is used, configure will stop with an error when depends are missing.

When it is not used, build will continue without wayland support. Previously, depends were missing and wayland support was not being built. So this major 9.0 feature was missing. Currently, depends are present, so wayland support would be built. However, if depends change, wayland support would again stop being built.

tiziodcaio commented on 2024-01-20 13:05 (UTC)

Yes @loathingkernel, now I will fix. When I saw @xiota adding them I was a bit confused by the sintax, I think it complicates things that might be simpler... Anyway, why it was added the --with-wayland flag? It appears to not be necessary as into https://gitlab.winehq.org/wine/wine/-/blob/wine-9.0/configure.ac?ref_type=tags#L1397

loathingkernel commented on 2024-01-20 12:36 (UTC) (edited on 2024-01-20 12:37 (UTC) by loathingkernel)

Please do not make PKGBUILDs configurable in terms of sources and build options. Yes, it might be useful but scripts on the AUR should ideally be easily inspect-able without requiring effort to decode the conditionals.

There is no good reason to use two different switches to alter sources and build options while making the script that much harder to quickly parse. The same consistency when updating a script could be achieved with a good diff tool.

xiota commented on 2024-01-18 02:30 (UTC)

Wayland support requires setting a registry variable. See Wine 9.0 Changelog.

wine reg.exe add HKCU\\Software\\Wine\\Drivers /v Graphics /d x11,wayland

yan12125 commented on 2023-12-18 15:20 (UTC)

Cool, thanks!

« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »