buildwine.py is a script to build Wine variants from source. It supports cross-compiler setups for
non-Intel architectures. Run with '--help' for usage.
By default, buildwine always builds shared WoW64 Wine (32-bit and 64-bit), except when cross-compiling (non-Intel).
Note the following defaults:
- building of tests is disabled, enable it by passing
--enable-teststo the script - integration of Wine-Mono is disabled when building from HEAD (no explicit
--version), enable it by passing--enable-mscoreeto the script
The script maintains a specific top-level directory structure to separate sources and build artifacts for various variants and host/target architectures.
Sources:
custom-install-x86_64
custom-src
...
mainline-src
mainline-src-1.3.28
...
staging-patches
staging-patches-4.0
staging-src
staging-src-4.0
...
mainline-src-5.5
mainline-src-reference-gitmirrorBuild directories:
custom-build-i686
custom-build-x86_64
...
mainline-build-1.3.28-i686
mainline-build-1.3.28-x86_64
...
mainline-build-aarch64
mainline-build-arm
...
mainline-build-i686
mainline-build-x86_64
...
staging-build-4.0-i686
staging-build-4.0-x86_64
...
staging-build-i686
staging-build-x86_64Install directories:
custom-install-x86_64
...
mainline-install-1.3.28-x86_64
...
mainline-install-5.5-x86_64
mainline-install-aarch64
mainline-install-x86_64
...
staging-install-4.0-x86_64
staging-install-x86_64Build Wine from current branch HEAD:
./buildwine.pyBuild a specific Wine release:
./buildwine.py --version=5.5Build Wine-Staging variant of a Wine release:
./buildwine.py --variant=staging --version=4.0Build a custom variant, useful when doing Git bisect:
./buildwine.py --variant=customBuild a range of Wine releases:
# build Wine 1.7.[51..53]
for i in 1.7.{51..53} ; do ./buildwine.py --version=$i --clean || break ; done
# build Wine 1.7.[40..49]
for i in `git -C mainline-src tag | sed -n 's/^wine-\(1.7.4[0-9]\)/\1/p' | \
sort -V` ; do ./buildwine.py --version=$i --clean || break ; doneTo better diagnose/debug build failures, pass --jobs=1 to the script.
See How to show missing development packages when building Wine from source.
Even though modern Wine doesn't require multilib for WoW64 build anymore, sometimes it's still desired (building older Wine versions). In case of multilib conflicts (yes, this is still a case in 2024!!!), you may need to force install 32-bit devel packages over 64-bit devel ones.
Example with Fedora 40, where glib2-devel.i686 can't be installed alongside glib2-devel-2.80.2-1.fc40.x86_64.
sudo dnf install glib2-devel.i686
Last metadata expiration check: 0:45:23 ago on Tue 14 May 2024 04:03:16 PM CEST.
Dependencies resolved.
=====================================================================================================================================================================================
Package Architecture Version Repository Size
=====================================================================================================================================================================================
Installing:
glib2-devel i686 2.80.2-1.fc40 updates 1.5 M
Transaction Summary
=====================================================================================================================================================================================
Install 1 Package
Total download size: 1.5 M
Installed size: 16 M
Is this ok [y/N]: >
Is this ok [y/N]: y
Downloading Packages:
glib2-devel-2.80.2-1.fc40.i686.rpm 3.5 MB/s | 1.5 MB 00:00
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total 1.2 MB/s | 1.5 MB 00:01
Running transaction check
Transaction check succeeded.
Running transaction test
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: Transaction test error:
file /usr/share/gir-1.0/GLib-2.0.gir from install of glib2-devel-2.80.2-1.fc40.i686 conflicts with file from package glib2-devel-2.80.2-1.fc40.x86_64Ugly workaround: Skip dnf but use rpm force install to install the downloaded package manually:
Fedora page for the offending package
sudo rpm -Uvh --force glib2-devel-2.80.2-1.fc40.i686.rpm
Verifying... ################################# [100%]
Preparing... ################################# [100%]
Updating / installing...
1:glib2-devel-2.80.2-1.fc40 ################################# [100%]See project home page LLVM/Clang/LLD based mingw-w64 toolchain for overview.
Main benefits:
- Wine builtin modules cross-compiled to PE format (no ELF hybrids as with GCC)
- symbol information generated in PDB format which can be used with many Windows debugging tools
Tarballs are available from LLVM/Clang/LLD mingw-w64 release downloads.
Make sure it can be found in path by prepending the bin directory from the unpacked tarball to the PATH environment variable.
For more information on how to create Poky SDK cross-toolchains see meta-winedev: Yocto layer for Wine cross-development.
Wine currently doesn't build with Yocto/Poky SDK cross-toolchains due to following bugs:
Apply the patches.
After that, configure needs to be updated. Since cross-compiling is done, a host-build for running wine tools must exist.
./buildwine.py --clean --force-autoconfInstall Poky SDK toolchain(s):
./build-$MACHINE/tmp/deploy/sdk/*-toolchain-*.sh -d sdk-install -yRegister the cross-toolchain in the shell environment.
For 64-bit ARM:
source sdk-install/environment-setup-aarch64*For 32-bit ARM:
source sdk-install/environment-setup-armv7*Build Wine for target arch.
./buildwine.py --cross-compile-prefix=$CROSS_COMPILE --disable-mingw --clean --force-autoconfLinks