[wellylug] Codeweavers Wine + Tansgaming WineX on same system

[Ilia Pavlenko]

Yes, actually, that's what I ended up with : two scripts:
/usr/local/bin/WINE and /usr/local/bin/WINEX;

where "WINE" script is:
WINEDLLPATH=/usr/local/Wine/lib:/usr/local/Wine/lib/wine
LD_LIBRARY_PATH=/usr/local/Wine/lib:$LD_LIBRARY_PATH
WINELOADER=/usr/local/Wine/bin/wine
WINESERVER=/usr/local/Wine/bin/wineserver /usr/local/Wine/bin/wine $1

and "WINEX" is:
WINEDLLPATH=/usr/local/WineX/lib
LD_LIBRARY_PATH=/usr/local/WineX/lib:$LD_LIBRARY_PATH
WINELOADER=/usr/local/WineX/bin/wine
WINESERVER=/usr/local/WineX/bin/wineserver /usr/local/WineX/bin/wine $1

so far so good :)

Ilia

On Sun, 29 Jun 2003, Ewen McNeill wrote:

> In message <Pine.LNX.4.31.0306291136060.19397-100000 at peresvet.sixpack.homeip.net
> >, Ilia Pavlenko writes:
> >What's the best way to make two forks of wine co-exist ?
> >Currently I got one in /usr/local/Wine/*, another in /usr/local/WineX/*,
> >however they conflict when they try to load "libwine.so". For wine to be
> >able to load "libwine.so" the path to it has to be entered into
> >/etc/ld.so.conf, but if I have two forks of wine
>
> You might be better putting _neither_ directory in your ld.so.conf, and
> using LD_LIBRARY_PATH and friends to add to the list that ld will use on
> a program-by-program (or run-by-run) basis.  You could, eg, use a couple
> of shell scripts to automate this process (ie, set LD_LIBRARY_PATH and
> friends, and then execute the rest of the command line).
>
> Ewen
>
> --
> Wellington Linux Users Group Mailing List: wellylug at lists.naos.co.nz
> To Leave:  http://lists.naos.co.nz/mailman/listinfo/wellylug
>