Wine

Wine (Wine Is Not an Emulator) is Article description::an application that allows Windows software to run on Linux and other POSIX-compliant operating systems. This article deals with installing, configuring, and maintaining a general purpose Wine environment on Gentoo.

Packaging details
As many Wine users know, there are often regressions or an application works better on one version of wine than another. Going forward, packaging in Gentoo will allow simultaneous installation of multiple versions of Wine.

Additionally, to expedite vanilla releases as well as permit multiple configurations for each Wine installation, the major patchsets have been split out into separate packages.

Quick start
For most users, worrying about the various packages and what they do should not be a concern.The split packaging and slotting is a power user feature, and most users will be OK with simply installing, which chooses which wine version for the user.

Wine variants

 * upstream Wine with no external patchsets.
 * (like if the old packaging forced USE="-staging -d3d9".)
 * Wine with Wine-Staging's patchset.
 * (like if the old packaging forced USE="+staging -d3d9".)
 * Wine with Ixit's Gallium Nine patchset.
 * (like if the old packaging forced USE="-staging +d3d9".)
 * Deprecated and unmaintained, available only via the Wine overlay. Use  instead.
 * Wine with any of the patchsets or flags.
 * (exactly like the old packaging regarding USE flags.)
 * Deprecated and unmaintained, available only via the Wine overlay.
 * wine-any exists to allow the user to build any combination that they'd like (like the old packaging). This means the user could use wine-any to use both Wine-Staging and Gallium Nine. Alternatively, the user could use wine-any to try out another configuration from other packages. For example, the user could build wine-vanilla without PulseAudio, and could build wine-any with PulseAudio. The sky is the limit on how a user may choose to use app-emulation/wine-any.

Choosing a variant

 * manages selection of a variant in such a way as to provide the best experience to the user. Most users don't want to be dealing with external patchsets. External patchsets may introduce bugs that don't exist in the vanilla Wine release and can make using Wine more complicated for the user. External patchsets also can be released up to a week or two after vanilla wine (or each other), meaning that the period for releases can be significantly slower for those using.


 * What if I want to manually choose a variant anyway? Which should I choose?
 * This really isn't a question that the authors of this document can answer. Typically, the logic works as follows:
 * Unless you need something more, choose.
 * If an application requires advanced features only available in Wine-Staging, choose.
 * If you do research online and find that Wine-Staging provides better performance for an application, choose.

USE flags
Users may also find information about specific USE flags required to run their applications here.

32-bit vs 64-bit
Invariably, users want to understand why they have to rebuild tons of packages to install Wine because they have to enable  on a lot of Wine's dependencies... This is unavoidable, and we must highly warn against disabling   and installing only with abi_x86_64 unless you really know what you are doing. Often, an application will have components that are 32-bit (or even 16-bit) and by installing Wine without 32-bit support, the user is left unable to install or launch an application. It is best to enable 32-bit support on a per-package basis, as indicated by the package manager, rather than globally.

Note that some dependencies of Wine need  set in the kernel config to work. Failing to do so will generate error messages of the kind: “The futex facility returned an unexpected error code.” during build or at runtime. Affected are for example the packages dev-libs/icu and sys-devel/llvm.

Environment variables
Traditionally, live (9999) ebuilds support setting the repository commit as an environmental variable. This poses some issues with an ebuild that has multiple upstream repositories. To work around this issue, Wine's live ebuilds support three environmental variables for individually configuring the commit that each repository checks out. The WineHQ repository is controlled by WINE_COMMIT, Wine-Staging repository by STAGING_COMMIT, and Ixit's Gallium Nine repository by D3D9_COMMIT. The *_COMMIT variables may contain either a commit hash from that repository or a git tag from that repository.

For example, one could select the WineHQ tag "wine-2.0-rc5" to emerge the 2.0 RC 5:

One could additionally pin Wine-Staging to the same release by finding the appropriate tag, "v2.0-rc5" and augmenting the previous as follows:

Other environmental variables, which affect Wine at runtime, are discussed below.

Emerge
Enable the USE flags of your choosing on the virtual and then on the variant selected (automatically by the virtual or manually by yourself) and the package:

or

Only versions classified as "stable" by upstream will be stabilized in Gentoo, and only as the variant, as external patchsets are not considered stable. Some users may opt to add Wine variants to their package.accept_keywords file to allow for installation of development versions of Wine.

Runtime environment variables
The environment variables of the shell that is started from are made accessible to the Windows/DOS processes. Some very useful Wine-specific variables include, but are not limited to, WINEPREFIX, WINEARCH , and WINEDEBUG.

See the and  manual entries for more detailed information concerning Wine's environment variables.

WINEPREFIX
To create a Wine prefix in a custom location (instead of ) without affecting the default:

The above would create a Wine prefix at.

WINEARCH
To create a 32-bit installation instead of the default (when built) 64-bit:

The Wine executable used could be anything that runs Wine, such as, which often makes sense while creating a clean, new prefix.

WINEARCH requires that Wine be built with the corresponding  flags.

WINEDEBUG
Essential in finding out why an application is misbehaving when the basic terminal output or messages boxes are not enough. See https://wiki.winehq.org/Debug_Channels for examples.

Configuration tools
The following tools include graphical and command line interfaces for managing Wine prefixes:


 * – Qt5 GUI configuration tool for Wine.
 * – Easy way to install DLLs needed to work around problems in Wine.

Automatically start wine on Windows executables
With the appropriate kernel support and a bit of system configuration, it is possible to automatically start wine when executing.

Kernel support for miscellaneous binary format is necessary as a prerequisite. See the Kernel section of the Embedded Handbook article.

systemd
The following file should be created so that systemd can register the correct service handler for Windows executables.

Upstream FAQs
Some upstream FAQ entries that users might find useful:


 * How to uninstall individual applications
 * How to remove a Wine prefix
 * How to prevent Wine from creating menu items

Troubleshooting
When a user encounters a problem with an application, they should try the latest development version to see if the unwanted behavior still exists. If Wine has been built with options such as  or , the Wine developers will likely be unable to help with the issue, and reports including output from such builds should not be reported to the Wine Bugzilla.

The  USE flag should be enabled for debugging builds.

For more directions on reporting bugs, see Bugzilla and Bugs at wiki.winehq.

Support
Users may find additional support in the channel on Libera.Chat.

External resources

 * – Wine related bugs.
 * WineHQ Wiki
 * Wine Application Database – Search for the game or program to install here to see if it is stable.
 * Wine Staging at GitHub