1 Installing distro packages

New versions of openSUSE ship with the Wine development release that was current at the time packages were frozen for release.

Up-to-date Wine packages are available through the Wine repository on the OBS. The package maintainer is Marcus Meissner. The repository includes packages for the biweekly releases of both Wine and Wine-staging, daily "snapshot" packages of git, and packages for wine-gecko and wine-mono. Simply add the repository to Yast2 or zypper and install as you would any other package.

Some notes about the openSUSE Wine packages:

The packages include winetricks, installed to /usr/bin/.

The packages include .desktop files for Wine's builtin programs (winecfg, notepad, etc.), which are not part of vanilla Wine. Report any problems with them to the package maintainer.

The distro does not package the stable branch; however, packages for the stable releases may be available from personal projects on the OBS. Note that these packages are not supported by either WineHQ or the distro package maintainer.

Restricted codecs needed by winegstreamer are available in the Packman repository.

2 Building Wine

2.1 On the OBS

If you merely wish to recreate the distro package with minor modifications (e.g., adding custom patches), the easiest way to do that is by branching the Emulators:Wine package on the OBS, applying whatever changes you wish to make to the spec file, and building from that. See the openSUSE Build Service Tutorial for information on how to use the OBS.

2.2 From Git

Building from git is necessary to run regression tests or test patches.

2.2.1 Cloning the Wine Git Repository

2.2.2 Build Tools and Dependencies

The information in this section is based on openSUSE Leap 42.2 and Wine 3.0-rc3. Exact package names may vary depending on your version of openSUSE, and new dependencies may be added in future Wine versions. Always check the output of ./configure to verify that you have all needed dependencies installed.

The following repositories should be enabled to obtain basic build tools and Wine's build dependencies:

OSS (the main repository; this one is required, and should already be set up on your system)

Update (recommended in order to have the most up-to-date versions; for most people, this should also already be set up)

Wine (recommended, as installing a distro package will pull in Wine's runtime dependencies)

The meta-package patterns-openSUSE-devel_basis will install the basic tools needed for building (gcc, make, flex, bison, etc.); on a 64 bit system, you will also need to install the patterns-openSUSE-32bit meta-package. You will also need to install git.

Dependencies

Installing the distro wine, wine-snapshot, or wine-staging package is the easiest way to install the libraries Wine depends on, as zypper or Yast2 will automatically pull them in.

Since the distro packages are built without SANE support, you will need to install the following package yourself:

sane-backends (if you want scanner support)

On a 64 bit system, you will also need to install

sane-backends-32bit (if you want scanner support)

In addition to the runtime dependencies, the following development packages are needed:

(Installing the wine-32bit-build-deps package will install most of the -32bit packages listed above.)

The glib2-devel-32bit packages for openSUSE versions 13.1, 13.2, and Leap 42.1 were missing the 32 bit header and pkgconfig files needed to compile 32 bit Wine with gstreamer support on a 64 bit system. The workaround was to extract the missing files from the i586 glib2-devel package and manually place the needed files in /usr/include and /usr/lib/pkgconfig. This problem has been fixed in Leap 42.2 and later. (See bug 973217)

After installing the above, you may need to make the following symlinks in /usr/lib (needed for libraries that do not have a -devel-32bit package):

The targets of the above symlinks may need to be adjusted depending on what version of the library you have installed.

Packages needed to build with HAL and OSSv4 support are not available from any of the openSUSE repositories, and ./configure will complain about it. Neither is needed on current versions of openSUSE; if those are the only things ./configure complains about, you are good to go.

2.2.3 Building 32 bit Wine

On a 32 bit system

After cloning the git repository, cd to the wine-git directory and run

CC="ccache gcc" ./configure --disable-tests

Check the output of ./configure to make sure there are no missing dependencies for features that you need. If there are, install them. Assuming all is well, just run

make

On a 64 bit system

After cloning the git repository, cd to the wine-git directory and run

Check the output of ./configure to make sure there are no missing dependencies for features that you need. If there are, install them. Assuming all is well, just run

make

2.2.4 Building Shared WoW64

If all your apps/games are 32 bit, there is no need to build 64 bit Wine at all unless you are interested in helping with testing. Simply follow the instructions in the preceding section to build 32 bit Wine on a 64 bit system.

Pure 64 bit Wine is not a supported configuration (and is generally useless, as most Windows apps are still 32 bit). For 64 bit support, you must build both 64 bit and 32 bit Wine in a shared WoW64 setup. This does not require a container or chroot on openSUSE, but the builds must be done out of tree, and in the order specified below.

1. Build the 64 bit side

Create a directory for the 64 bit build and run configure from within that directory:

Double check the output of configure for any missing 32 bit dependencies and install any that are needed. If all is well, run

make

from within the wine32 directory.

2.3 From a Source Tarball

Building from a source tarball offers less flexibility than git while requiring the same amount of work

If you prefer to build from a source tarball rather than git, follow the instructions above for building from git, but instead of cloning the git repository, download the tarball for the version you want from http://dl.winehq.org/wine/source/ and extract it. Substitute the source directory for the wine-git directory when following the instructions.

The tools directory contains an obsolete script called wineinstall. Do not use this script, as it has not been updated in years and cannot build 64 bit Wine.