Winelib and static-build

Alan Nisota alannisota at gmail.com
Thu Oct 23 21:22:12 CDT 2008


I have a project (http://code.google.com/p/coreavc-for-linux) which is a 
linux executable which provides access to Windows DirectShow filters 
(despite its name, the program should work with many Directshow Video 
codecs).  Currently, it builds against a forked version of mplayer's 
'loader' library, but there are stability problems with this solution 
(the 'loader' library many hacks to provide just enough infrastructure 
to the codec, and debugging issues is difficult due to the binary nature 
of the filter)

I found that building against winelib works quite well (once I found 
that I needed to define __MINGW__) and the stability is much better (in 
fact the program seems rock-solid now).

The problem is that I normally provide a static binary so that users on 
x86-64 can install it easily without needing a 32bit build environment 
and without me needing to provide packages for every distribution.  The 
host app (Mythtv, mplayer, xine), can still be 64bit, since I use 
shared-memory and semaphores to communicate, and this works fine between 
32bit and 64bit apps.  It seems that wine is available for most 32 and 
64bit distros (built in a 32bit chroot in the x86-64 case).  My question 
is, is it possible to do a static-compile of my winelib app that will 
run properly  on multiple distros and interface with wine correctly?

I'd be building against a fixed version of wine, (say 1.1.6 or 1.0, or 
whatever) but would want compatibility with whatever version the user's 
distro happens to provide (within reason).  Is this possible?

Sorry if this doesn't exactly belong on the dev list, it  didn't seem to 
fit the user list either, and I couldn't find a better place.




More information about the wine-devel mailing list