Painkiller Jane, on Apr 21 2004, 03:06 PM, said:
maybe it's possible to compile only the comctl32.so and replace the file of a installed rpm'ed wine instead of compiling the whole thing?
but i guess that implies certain gpl requirements have to be followed if one rips out that particular part of the XO wine source.
I was thinking the same thing. CodeWeavers is distributing that source code under LGPL (I can't find anything that makes exclusions on their particular contributions in the distro docs) so it appears we can safely use their code or make patches consisting of their changes if necessary.
Reading on the Wine list though, replacing one of Wine's internal libs with a different version could really screw things up. I suppose there's no harm in trial-and-error though. I've already installed and re-installed Wine/XO probably 2 dozen times during the course of this project.
Your socket trouble was with dll's other than comctl32 however. If we're looking at replacing more than a handful of dll's, then we might as well just use CodeWeavers' entire codebase for the build. We know it works together, at least for our purposes.
I've discovered it's possible to have more than one Wine implementation on your box. Because the CodeWeavers version is so old, I can make the installation script ask the user if they are already using Wine and if they would like a parallel installation expressly for eMule. Or they could optionally elect to uninstall their current Wine version, or whatever. A Wine installation is tiny anyhow, no harm in having multiples.
Just kinda thinking out loud here...