Difference between revisions of "Wine-Staging"

From WineHQ Wiki
Jump to: navigation, search
(change the bug links to just show the Wine Staging bug list.)
(Downloads)
 
(7 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
Wine Staging is the testing area of winehq.org. It contains bug fixes and features, which have not been integrated into the development branch yet. The idea of Wine Staging is to provide experimental features faster to end users and to give developers the possibility to discuss and improve their patches before they are integrated into the main branch.
 
Wine Staging is the testing area of winehq.org. It contains bug fixes and features, which have not been integrated into the development branch yet. The idea of Wine Staging is to provide experimental features faster to end users and to give developers the possibility to discuss and improve their patches before they are integrated into the main branch.
  
Wine Staging is maintained as a set of patches which has to be applied on top of the corresponding Wine development version. Package maintainers can decide if they want to include our full patchset, or only want to cherry-pick patches for specific bugs. Our current version includes fixes for about 450 bugs and over 900 patches total, and new patches are added frequently. Features and bugfixes available in Wine-Staging 3.8 are for example:
+
Wine Staging is maintained as [https://github.com/wine-staging/wine-staging a set of patches] which has to be applied on top of the corresponding Wine development version. Package maintainers can decide if they want to include our full patchset, or only want to cherry-pick patches for specific bugs.
  
    CSMT (Commandstream multithreading) for better graphic performance
+
== Installation ==
    CUDA / PhysX / NVENC Support for NVIDIA graphic cards
+
    DXVA2 GPU video decoding (experimental)
+
    Direct3D 10/11 enhancements
+
    EAX 1 support
+
    Fixes for various upstream regressions
+
    GTK 3 theming support
+
    macOS preloader
+
    Performance improvements for IO-heavy programs and memory allocation functions
+
    S3 texture compression (DXTn) support
+
    Support for allocating more than 32 GB of memory
+
    Support for installing MSU files
+
    Various improvements to d3dx9
+
    Various speed improvements (shared memory, RT priority)
+
    Windows ACL support
+
  
 +
Pre-compiled Staging packages for most major distributions are available on the [https://wiki.winehq.org/Download Download] page. Instructions for installing Staging are given under each distribution that provides it.
 +
 +
== Building from source==
 +
 +
Since Wine-Staging is maintained as a set of patches rather than a forked repository, the process of building is slightly different. You will first need a vanilla Wine source tree and the required dependencies; for instructions see [[Building Wine]]. Note that Staging adds some optional dependencies which are necessary for certain additional features. You will also need the Staging "source"; this can be cloned or downloaded from [https://github.com/wine-staging/wine-staging the GitHub page].
 +
 +
Once you have obtained the sources, you will need to apply the Staging patches of your choice (or all of them) on top of the Wine source tree. You can do this using the provided <tt>patches/patchinstall.sh</tt> script; see its options with --help for detailed instructions. If you apply patches manually, take note that you will also need to run <tt>autoreconf -f</tt> and <tt>tools/make_requests</tt>, as such generated changes are not included in Staging patches. Be warned that an individual version of the Staging repository will ''only'' successfully apply against the upstream Wine commit it was last rebased against.
 +
 +
After you have applied patches, compilation proceeds as usual for upstream Wine; refer to [[Building Wine]] for detailed instructions.
  
 
== Quick Links ==
 
== Quick Links ==
Line 27: Line 22:
 
{| class="wikitable" border="1"
 
{| class="wikitable" border="1"
 
|-
 
|-
| [[File:icon-usage.png]]
+
| [[File:icon-usage.png]]https://github.com/wine-staging/wine-staging
 
| [[Wine-Staging_Usage|Usage]]
 
| [[Wine-Staging_Usage|Usage]]
 
|-
 
|-
Line 39: Line 34:
 
| [https://bugs.winehq.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=STAGED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=RESOLVED&list_id=610554&product=Wine-staging&query_format=advanced Bugs]
 
| [https://bugs.winehq.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=STAGED&bug_status=REOPENED&bug_status=NEEDINFO&bug_status=RESOLVED&list_id=610554&product=Wine-staging&query_format=advanced Bugs]
 
|}
 
|}
 +
 +
== See Also ==
 +
[https://github.com/wine-staging/wine-staging Wine-staging GitHub repository]

Latest revision as of 10:12, 18 November 2018

What is Wine Staging?

Wine Staging is the testing area of winehq.org. It contains bug fixes and features, which have not been integrated into the development branch yet. The idea of Wine Staging is to provide experimental features faster to end users and to give developers the possibility to discuss and improve their patches before they are integrated into the main branch.

Wine Staging is maintained as a set of patches which has to be applied on top of the corresponding Wine development version. Package maintainers can decide if they want to include our full patchset, or only want to cherry-pick patches for specific bugs.

Installation

Pre-compiled Staging packages for most major distributions are available on the Download page. Instructions for installing Staging are given under each distribution that provides it.

Building from source

Since Wine-Staging is maintained as a set of patches rather than a forked repository, the process of building is slightly different. You will first need a vanilla Wine source tree and the required dependencies; for instructions see Building Wine. Note that Staging adds some optional dependencies which are necessary for certain additional features. You will also need the Staging "source"; this can be cloned or downloaded from the GitHub page.

Once you have obtained the sources, you will need to apply the Staging patches of your choice (or all of them) on top of the Wine source tree. You can do this using the provided patches/patchinstall.sh script; see its options with --help for detailed instructions. If you apply patches manually, take note that you will also need to run autoreconf -f and tools/make_requests, as such generated changes are not included in Staging patches. Be warned that an individual version of the Staging repository will only successfully apply against the upstream Wine commit it was last rebased against.

After you have applied patches, compilation proceeds as usual for upstream Wine; refer to Building Wine for detailed instructions.

Quick Links

Here are some links to the most important topics.

Icon-usage.pnghttps://github.com/wine-staging/wine-staging Usage
Icon-config.png Configuration
Icon-contribute.png Contributing
Icon-bug.png Bugs

See Also

Wine-staging GitHub repository