Wine: Difference between revisions
imported>Haslersn m Adapted headline to the previous change |
imported>Nh2 Explain when wineWow is needed |
||
Line 22: | Line 22: | ||
]; | ]; | ||
}</syntaxhighlight> | }</syntaxhighlight> | ||
If you get the error <code>wine: '/path/to/your/wineprefix' is a 64-bit installation, it cannot be used with a 32-bit wineserver.</code>, then you need the 64-bit (<code>"wineWow"</code>) build. | |||
The <code>override</code> method is mentioned in [https://nixos.org/nixos/manual/index.html#sec-customising-packages the manual]. | The <code>override</code> method is mentioned in [https://nixos.org/nixos/manual/index.html#sec-customising-packages the manual]. |
Revision as of 11:24, 3 December 2019
32-bit and 64-bit Support
On x86_64-linux, the wine package supports by default both 32- and 64-bit applications. On every other platform, the wine package supports by default only 32-bit applications.
These defaults can however be overwritten like this:
{
environment.systemPackages = with pkgs; [
# ...
# support both 32- and 64-bit applications
(wine.override { wineBuild = "wineWow"; })
# support 32-bit only
# (wine.override { wineBuild = "wine32"; })
# support 64-bit only
# (wine.override { wineBuild = "wine64"; })
# wineStaging accepts the wineBuild argument, too
# (wineStaging.override { wineBuild = "wineWow"; })
];
}
If you get the error wine: '/path/to/your/wineprefix' is a 64-bit installation, it cannot be used with a 32-bit wineserver.
, then you need the 64-bit ("wineWow"
) build.
The override
method is mentioned in the manual.