From WineHQ Wiki
Revision as of 16:09, 14 January 2016 by RosanneDiMesio (talk | contribs) (Created page with "== Installing WineHQ packages == First add the repository: ''Fedora 22:'' dnf config-manager --add-repo https://dl.winehq.org/wine-builds/fedora/22/winehq.repo ''Fedora 2...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Installing WineHQ packages

First add the repository:

Fedora 22:

dnf config-manager --add-repo https://dl.winehq.org/wine-builds/fedora/22/winehq.repo

Fedora 23:

dnf config-manager --add-repo https://dl.winehq.org/wine-builds/fedora/23/winehq.repo

Install package (example for the development branch):

dnf install winehq-devel

If you prefer to use the Staging branch, replace `winehq-devel` with `winehq-staging` in the line above.

Build Dependencies

Fedora 22 or Later

(Note: This section is incomplete.)

Consider running this command (provided by ["ZhenboLi"], tested on Fedora 23)

sudo dnf install alsa-plugins-pulseaudio.i686 glibc-devel.i686 libgcc.i686 libX11-devel.i686 freetype-devel.i686 libXcursor-devel.i686 libXi-devel.i686 libNX_Xext-devel.i686 libXext-devel.i686 libXxf86vm-devel.i686 libXrandr-devel.i686 libXinerama-devel.i686 mesa-libGLU-devel.i686 mesa-libOSMesa-devel.i686 libXrender-devel.i686 libpcap-devel.i686 ncurses-devel.i686 libzip-devel.i686 lcms2-devel.i686 zlib-devel.i686 libv4l-devel.i686 libgphoto2-devel.i686 libcapifax-devel.i686  cups-devel.i686 libxml2-devel.i686 openldap-devel.i686 libxslt-devel.i686 gnutls-devel.i686 libpng-devel.i686 flac-libs.i686 json-c.i686 libICE.i686 libSM.i686 libXtst.i686 libasyncns.i686 libedit.i686 liberation-narrow-fonts.noarch libieee1284.i686 libogg.i686 libsndfile.i686 libuuid.i686 libva.i686 libvorbis.i686 libwayland-client.i686 libwayland-server.i686 llvm-libs.i686 mesa-dri-drivers.i686 mesa-filesystem.i686 mesa-libEGL.i686 mesa-libgbm.i686 nss-mdns.i686 ocl-icd.i686 pulseaudio-libs.i686 python-talloc.x86_64 sane-backends-libs.i686 tcp_wrappers-libs.i686 unixODBC.i686 samba-common-tools.x86_64 samba-libs.x86_64 samba-winbind.x86_64 samba-winbind-clients.x86_64 samba-winbind-modules.x86_64 mesa-libGL-devel.i686 fontconfig-devel.i686 libXcomposite-devel.i686 libtiff-devel.i686 openal-soft-devel.i686 mesa-libOpenCL-devel.i686 opencl-utils-devel.i686 alsa-lib-devel.i686 gsm-devel.i686 libjpeg-turbo-devel.i686

Also, you need some packages from rpmfusion

gstreamer-plugins-base.i686 gstreamer-plugins-base.x86_64 gstreamer.i686 gstreamer.x86_64 libmpg123-devel.i686 gstreamer-plugins-base-devel gstreamer-plugins-base-devel.i686


Thanks to Fedora's multilib arrangement, once you have the dependencies, building either a plain 32-bit or WoW64 version of Wine should be straight-forward. The appropriate sections on BuildingWine should list all the steps.

A Bit of History

Fedora has a unique history among GNU/Linux distributions that partly explains its goals and relationship to other distros. It initially began as a minor distro, Fedora Linux, that would test and package extra software on top of the venerable RedHat distro (now technically Red Hat Enterprise Linux). Around the same time though, Red Hat Inc. decided to focus on very stable releases with long-term support for enterprises.

At first, the company tried directly managing a more fluid branch geared towards desktops, but many non-subscribing PC users began switching to Fedora Linux. At that point, Red Hat made the farsighted decision to cooperate with the Fedora Linux community on experimental work, and the Fedora project was born. The resulting distribution was originally called "Fedora Core" before being renamed simply "Fedora" after a few years.

Today, Fedora is the work of a worldwide community of volunteers, but Red Hat Inc. still contributes a great deal to the project through both collaboration and financial support. In a bit of a role-reversal, Fedora is also now effectively upstream of its parent distro; RedHat (and its child distros) will periodically branch off a new Fedora release, then after much more testing and bug-fixing, provide a new release to their more stability-minded users.

See Also