Wineskin Support Forum Help

Forums » Wineskin Support Forum » Automatic Wine building and Wine Staging project

Automatic Wine building and Wine Staging project

doh123, have you ever considered automatizing the process of building Wineskin engines? So that even if you don't have time, the users would get fresh engines through Wineskin Winery. And if something goes wrong, you could always build a given engine manually. Maybe you might take some hints from MacPorts(external link), I think they already build Wine automatically.

I also would like to draw your attention to this interesting project--Wine Staging(external link). As they put it: "Wine Staging (formerly wine-compholio) is a special wine version containing bug fixes and features, which are not yet available in regular wine versions. The idea behind Wine Staging is to provide new features faster to end users and to give developers the possibility to discuss and improve their patches before they are sent upstream". Possibly you could create some builds (now or in the future) based on their patchset?

I could write a script that checks for a new version, downloads it if found, and builds the engine... then uploads it to the server so Winery will see it.  I'll think about doing that, as it would save some time in the long run, and wouldn't be too difficult to do.

I've been trying to shy away from building too many Wine engines besides normal Wine and Crossover's... If you find there are certain major reasons to build a specific version from Wine Staging, I don't mind doing a special one here and there for specific reasons, but I don't really want to get in the habbit of making several different forks.


I could write a script that checks for a new version, downloads it if
found, and builds the engine... then uploads it to the server so Winery
will see it.  I'll think about doing that, as it would save some time in
the long run, and wouldn't be too difficult to do.



Any news about that?!?


It could be a great help for the community


Would be great to have wine-staging builds available. These are what fedora is shipping.


I'm one of the Wine Staging developers and would like to offer my help. I know maintaining Wine versions is a lot of effort, so I can perfectly understand that you want to keep the number of versions as small as possible. Nevertheless it seems like there are a lot of people interested (was asked via IRC already several times), so I would also vote for this idea. ;)

If there are any technical issues or questions you have, just contact me (via email or in our IRC channel #wine-staging on Freenode) or open a discussion in our bugtracker (bugs.wine-staging.com).




Hi Sebation, I've downloaded your wine-staging-master release for 1.7.39 and now have a working engine for Wineskin. Are there any important registry values that will help us take full advantage of the implemented changes?




sorry for the delayed response, but somehow I got no notification email, although I entered it correctly. ^^

There are indeed a couple of registry keys, the most important ones:

* Dll Redirects, see https://github.com/wine-compholio/wine-staging/wiki/DLL-Redirects.

The keys are



The key/value pairs all have type REG_SZ, the key is the name of the old dll and the value is the name of the new replacement dll. For example wined3d="wined3d-csmt.dll".

* CSMT, see https://github.com/wine-compholio/wine-staging/wiki/CSMT.

By default CSMT is off, it has to be enabled using a Dll Redirct (as explained above). When wined3d="wined3d-csmt.dll" is present in the list of dll redirects it is enabled, otherwise off.

* Fast Sound Mixer, see https://github.com/wine-compholio/wine-staging/wiki/Misc

Can be customized by setting


to a DWORD specifying the number of buffers. When the application tries to mix more buffers than the specified number, the fast sound mixer will be used instead of the slow (but more exact) one. This is mainly a performance optimization, setting it 0 will always use the fast sound mixer.

* Environment variable STAGING_WRITECOPY.

By setting it to a nonzero value (for example 1) it will activate the fix for https://bugs.winehq.org/show_bug.cgi?id=29384. Using registry values was not possible because the value is required directly on the startup of Wine. The bugfix is behind an environment variable switch because there is a high risk that it reveals additional Wine bugs.


There are a couple more settings and features, but they might not work correctly on MacOS yet. CUDA for example was not tested on MacOS so far (and might need some changes to be compatible), but we would really appreciate if some people experienced with building wine could work with us together, to get that done. The newly introduced feature for shared memory wineserver communication is also not available yet, because it uses a specific kernel feature, which is not present on MacOS. We are planning to add compatibility code for other operating systems soon.

If you have any additional questions, just ask.

Best regards,



It would be nice to the Sebastian read this discussion again and joined us here:


He could lend a hand to many ...



Post new message

Attach file Maximum size: 10.00 Mb
Post new reply

Show posts: