[RFC PATCH 0/5] XAudio PE conversion.

Rémi Bernon rbernon at codeweavers.com
Mon Jun 28 08:49:39 CDT 2021


On 6/28/21 3:15 PM, Jacek Caban wrote:
> On 6/25/21 2:54 PM, Rémi Bernon wrote:
>> Developing on both sides is going to be even more inconvenient than 
>> the canonical Linux way where we have to build the dependencies with 
>> MinGW first, install them locally somewhere, and point Wine where it 
>> can find the headers and import libs.
> 
> Majority of developers work on Wine itself and for them we could provide 
> pre-built static libs and/or they would just build them once in a while, 
> install and have multiple Wine builds use them.
> 
> Full bootstrap would indeed require 3-step process and it's probably 
> what you'd want when working on dependencies themselves. But we could 
> make 'wine-addons' build system optionally take care of building both 
> addons and Wine itself, which could hide that in in a single make 
> invocation.
> 
> That said, if we can make it work nice inside Wine itself, I'm not 
> against it. I just fear that it won't be pretty...
> 

It may be easier to use this wine-addons project to aggregate all the 
required dependencies, maintain the required glue (possibly ugly, but I 
don't think it has to be), and more properly expose their versions.

Wine build would then be pointed to the wine-addons source with a 
configure flag, or consider the dependencies as missing.

Of course, pre-built could be provided too, but I'm not sure if it's 
even worth the trouble if the build is straightforward (and not much 
longer).
-- 
Rémi Bernon <rbernon at codeweavers.com>



More information about the wine-devel mailing list