(Remove winezeug entry; now on its own page) |
No edit summary |
||
(16 intermediate revisions by 6 users not shown) | |||
Line 1: | Line 1: | ||
__NOTOC__ | |||
If you are interested in downloading the Wine source code, you can clone portions of the source tree to your computer with [http://git-scm.com/ Git]. There is a [[GitWine|tutorial]] on how to use Git with the Wine program source | The source code for Wine, all Wine websites, and supplementary web tools can be found online. You can explore the project's main source tree and commit history (all the way back to the first version in 1993) at the [https://gitlab.winehq.org/wine/wine Wine git tree]. You can also use the [http://source.winehq.org Wine cross-reference], although this only goes back to Wine v1.0. | ||
If you are interested in downloading the Wine source code, you can clone portions of the source tree to your computer with [http://git-scm.com/ Git]. There is a [[GitWine|tutorial]] on how to use Git with the Wine program source. The repositories are hosted on the [https://gitlab.winehq.org WineHQ Gitlab]: | |||
{| class="wikitable" | {| class="wikitable" | ||
|+Current Repositories | |||
| [https://gitlab.winehq.org/winehq/appdb appdb.git] || Code for the AppDB site and database | |||
|- | |||
| [https://gitlab.winehq.org/winehq/bugzilla bugzilla.git] || Code for Wine's bugzilla site and database | |||
|- | |||
| [https://gitlab.winehq.org/wine/fontforge fontforge.git] || A custom version of the [http://fontforge.sourceforge.net/ FontForge editor] for Wine fonts | |||
|- | |- | ||
| | | [https://gitlab.winehq.org/winehq/tools tools.git] || The various webtools used to maintain parts of the Wine site | ||
|- | |- | ||
| | | [https://gitlab.winehq.org/wine/vkd3d vkd3d.git] || 3D graphics library with an API similar to Direct3D 12 but a [https://www.khronos.org/vulkan/ Vulkan] backend | ||
|- | |- | ||
| | | [https://gitlab.winehq.org/winehq/winehq website.git] || The WineHQ website code | ||
|- | |- | ||
| | | [https://gitlab.winehq.org/wine/wine wine.git] || The source for the actual Wine program | ||
|- | |- | ||
| | | [https://gitlab.winehq.org/wine/wine-gecko wine-gecko.git] || The source code for the Wine Gecko engine | ||
|- | |- | ||
| | | [https://gitlab.winehq.org/wine/wine-staging wine-staging.git] || The Wine staging code | ||
|} | |||
{| class="wikitable" | |||
|+Obsolete Repositories | |||
| docs.git || Contains the SGML files formerly used for the Wine User's, Winelib User's, and Wine Developer's guides. These documents have been ported to the wiki and the SGML files will not be updated. | |||
|} | |||
== GitHub == | |||
The wine-mono source code and WineHQ packaging scripts are hosted on GitHub. | |||
{|class="wikitable" | |||
|wine-mono || https://github.com/madewokherd/wine-mono | |||
|- | |- | ||
| wine | |wine-packaging || https://github.com/wine-compholio/wine-packaging | ||
|} | |} | ||
== This Wiki == | |||
Whenever we use an existing framework in WineHQ, we try to keep the imported code as close to upstream as possible. This is particularly true of the Wine Wiki, which is a vanilla [https://www.mediawiki.org/wiki/MediaWiki MediaWiki] installation running our freshest [http://getbootstrap.com/ Bootstrap]-based theme for WineHQ. All CSS or javascript should come from one of those two sources (possibly including MediaWiki extensions or standard JS libraries like [https://jquery.com/ jquery]). | |||
== Alternative | == Alternative Repositories == | ||
There are actually several other repositories for Wine scattered around the internet, and in some situations, these alternative repos can be very useful. However, if you want to submit patches to the official upstream version of Wine, remember you must go through the mailing list (as described in [[Submitting Patches]]). | There are actually several other repositories for Wine scattered around the internet, and in some situations, these alternative repos can be very useful. However, if you want to submit patches to the official upstream version of Wine, remember you must go through the mailing list (as described in [[Submitting Patches]]). | ||
* (Via | * (Via HTTPS) You can find (bcompressed) copies of all Wine releases, either as complete code or incremental diffs, in the [https://dl.winehq.org/wine/source/ source folder of WineHQ's Download site]. | ||
* (ibiblio.org) Starting with v1.7, there are also source tarballs of Wine releases at [http://mirrors.ibiblio.org/wine/source/ ibiblio.org]. | * (ibiblio.org) Starting with v1.7, there are also source tarballs of Wine releases at [http://mirrors.ibiblio.org/wine/source/ ibiblio.org]. | ||
* (Github Fans) The WineHQ git repo also has an [https://github.com/mirrors/wine official mirror on Github]. | * (Github Fans) The WineHQ git repo also has an [https://github.com/mirrors/wine official mirror on Github]. | ||
* (Sundry Forks and Hacks) [[JanZerebecki]] maintains an up-to-date mirror of [http://repo.or.cz/w/wine.git Wine at repo.or.cz], along with several branches that developers have created over the years to test ideas. | * (Sundry Forks and Hacks) [[JanZerebecki]] maintains an up-to-date mirror of [http://repo.or.cz/w/wine.git Wine at repo.or.cz], along with several branches that developers have created over the years to test ideas. | ||
[[Category:Data]] [[Category:Development]] | [[Category:Data]] [[Category:Development]] |
Latest revision as of 11:21, 20 October 2022
The source code for Wine, all Wine websites, and supplementary web tools can be found online. You can explore the project's main source tree and commit history (all the way back to the first version in 1993) at the Wine git tree. You can also use the Wine cross-reference, although this only goes back to Wine v1.0.
If you are interested in downloading the Wine source code, you can clone portions of the source tree to your computer with Git. There is a tutorial on how to use Git with the Wine program source. The repositories are hosted on the WineHQ Gitlab:
appdb.git | Code for the AppDB site and database |
bugzilla.git | Code for Wine's bugzilla site and database |
fontforge.git | A custom version of the FontForge editor for Wine fonts |
tools.git | The various webtools used to maintain parts of the Wine site |
vkd3d.git | 3D graphics library with an API similar to Direct3D 12 but a Vulkan backend |
website.git | The WineHQ website code |
wine.git | The source for the actual Wine program |
wine-gecko.git | The source code for the Wine Gecko engine |
wine-staging.git | The Wine staging code |
docs.git | Contains the SGML files formerly used for the Wine User's, Winelib User's, and Wine Developer's guides. These documents have been ported to the wiki and the SGML files will not be updated. |
GitHub
The wine-mono source code and WineHQ packaging scripts are hosted on GitHub.
wine-mono | https://github.com/madewokherd/wine-mono |
wine-packaging | https://github.com/wine-compholio/wine-packaging |
This Wiki
Whenever we use an existing framework in WineHQ, we try to keep the imported code as close to upstream as possible. This is particularly true of the Wine Wiki, which is a vanilla MediaWiki installation running our freshest Bootstrap-based theme for WineHQ. All CSS or javascript should come from one of those two sources (possibly including MediaWiki extensions or standard JS libraries like jquery).
Alternative Repositories
There are actually several other repositories for Wine scattered around the internet, and in some situations, these alternative repos can be very useful. However, if you want to submit patches to the official upstream version of Wine, remember you must go through the mailing list (as described in Submitting Patches).
- (Via HTTPS) You can find (bcompressed) copies of all Wine releases, either as complete code or incremental diffs, in the source folder of WineHQ's Download site.
- (ibiblio.org) Starting with v1.7, there are also source tarballs of Wine releases at ibiblio.org.
- (Github Fans) The WineHQ git repo also has an official mirror on Github.
- (Sundry Forks and Hacks) JanZerebecki maintains an up-to-date mirror of Wine at repo.or.cz, along with several branches that developers have created over the years to test ideas.