WineBuild Requests

What is it?

This is a free service that we (the PlayOnLinux team) are happy to offer to you.
This service allows you to make a custom Wine build, and to allow other members of the PlayOnLinux community to benefit from it.
You don't need to know how to compile Wine, we do all the job for you! When it's done, the patched build will be available for everyone in the Wine Version manager (so you can also use it in a script).

How to use it?

First, you have to find a name for your build (eg: cnc3-kane).
Second, you have to put all patches that you want applied into a zip file.
Be careful while naming patch files and hosting the zip, there are some restrictions! (look at #1 & #2)
Third, you have to know which version of Wine you want this special build based on (eg: Wine 1.1.44).
Finally, fill the form: here!
Once you have made your request, you will be informed by mail when changes happen (start of build, end of build, error, ...) .

Who can use it?

Every registered user of this site!

Other information you should know

This is NOT an instant build service! Requests will be processed in order (first request to last request).
If ten days after you made a request you haven't any information about your build, then you can ring an alarm to the WineBuild team because there is probably a problem.

If we find out that you are using this service for any use that isn't approved, you can be excluded from this website. But I'm sure that you aren't evil, so there is no reason for us to ban you :-).

Appendix

Note #1 -- naming patch files

The name of the patch you want applied must follow this model:
XX-description-words.patch
In which XX is a two-digit number (so you can apply 100 patches numbered from 00 to 99).
The second part is a description, it has to be few words that describe what the patch does.
You can use alphanumerical characters, underscores and hyphens.
The patch files must end in '.patch'. Any file that doesn't respect this naming convention will NOT be applied.
EDIT: Read also Note #3.

Note #2 -- hosting the zip file

The zip file can be hosted anywhere on the Web.
But the file will be downloaded automatically, so it has to be a direct download available trough FTP or HTTP(S).
Please note that the URL must end in '.zip'. In other words, 'http://perdu.com/attachment.php?id=1234' isn't valid, but http://perdu.com/patch.zip' is valid.
If you don't have any idea for hosting, you can send the file by mail to the PoL team (specifically to MulX or Tinou).

Note #3 -- patch files with apply.lst

It's also possible to give the list of patch that need to be applied into an apply.lst file.
Each line should match with the exact name of patch file that will be included in your zip.
This file should be in the zip with other patch.
If this file is present patch will be applied in order (first line to end of file) and naming is more easy.

Key to the status codes

• 0 Queued
• 1 Starting
• 2 Build done, waiting for upload
• 3 Upload done, you can use it into PlayOnLinux
• 10 Unknown error occured. Read the log file, there may be some explanation. You can also contact the WineBuild Team for more information
• 11 You have selected a bad version of Wine. Since this is probably an internal error, you can contact the WineBuild Team ASAP.
• 12 The name you entered isn't valid.
• 13 The URL you entered to download a patch isn't valid. Check that your URL ends in .zip and starts with HTTP or FTP. You can contact the WineBuild Team if you need more explanations.
• 14 We downloaded the link, but it's not a zip file! Your link probably disallows direct downloads...
• 15 There is a problem with the unzip. Maybe it's corrupted or password protected?
• 16 We can't find any patch in your zip file! Check that you respected the naming convention
• 17 There is an error with the signature file for Wine. This is probably an internal error
• 21 There is a problem with the server when downloading the zip file. We don't know the size of the file
• 22 There is a problem with the server when downloading the zip file. The server says that the file is bigger than 5 MB
• 23 We downloaded the zip file, but it's bigger than 5 MB
• 24 There is an error while downloading the zip file. Read the log for more information
• 51 The configuration script ended with an error
• 52 Command make depend failed
• 54 Command make failed
• 58 A patch modifies the configuration script. This isn't allowed for security reasons. If you think this is a mistake, contact the WineBuild Team
• 66 There was an error while applying your patches

Who is part of the WineBuild Team?

Currently, there is only MulX. (Yes, I know I'm not a team on my own...)

Edited by MulX

Very cool! So how do i see what custom builds have been made?

Currently there is nothing to view only custom build.
But in PlayOnLinux WinVersion Manager you can found them quickly because their name was always "x.y.z-customName" -> eg 1.3.1-ubi-drm

There is also a new method for request pass list of patch, I have to edit my message for add explanation ... but for now no time :S

Hi. I'm working on patch to fix EE for wine:

http://source.winehq.org/source/dlls/dinput/mouse.c

I'm reading up on how to compile wine. I have quick hack to test, one line to change. I have a better idea to be more flexible with other games. I need to add a command line parm to pass to this if possible. I need to test values quickly without recompiling.

Thanks...

Name: wine_1.3.35_MSP

Hi there! I have ever build a wine version for League of legends, wine-1.3.36 with the ole patch, can I give it to you just like that or I need to give just the links for the wine version and the patch version?

so this is the patch file: http://www.filehosting.org/file/details/303466/ole-force-inproc-instead-of-local.patch
the wine version: http://sourceforge.net/projects/wine/files/Source/wine-1.3.36.tar.bz2

I dunno if it's good like that, sorry if it's not good! :s

Thanks!

Name: wine-1.3.36-LeagueofLegends

>Hi there! I have ever build a wine version for League of legends, wine-1.3.36 with the ole patch, can I give it to you just like that or I need to give just the links for the wine version and the patch version?

If you talking to me, I finally have setup that works. No changes to the mouse code are having any effect. EE doesn't use "dinput.dll". I'm sure. Someone suggested checking the x11 code in wine.