On Mon, Aug 28, 2000 at 01:29:42PM -0400, Michael Cardenas wrote:
>
> > Hello again.
> >
> > I'm working on renaming our versions of the wine libs, so that the corel
> > and deneba installations do not break each other. My question is, what is
> > the right way to do this?
> >
> > I have been working for a week on changing shell32.dll to cv7shell32.dl,
> > or really changing libshell32.so to libcv7shell23.so
> >
> > I did it by doing the following:
> > 1. changing the directory name from shell32 to cv7shell32
> > 2. modifying the following files to refer to cv7shell32
> > /wine/Makefile.in
> > /wine/dlls/Makefile.in
> > /wine/dlls/cv7shell32/Makefile.in
> > /wine/dlls/cv7shell32/shell32.spec
> > /wine/configure
> > (applicationDir)/.winerc
> > 3. changing all attempts to LoadLibrary("shell32.dll") to
> > LoadLibrary("cv7shell32.dll")
> >
> > but it still didn't work! Not only did the library not get loaded, but
> > other libraries also did not load after changing the name of the lib.
> > I suspect this is going to be a problem for anyone else who is going to
> > make winelib applications. I think it's so common that we should have a
> > configure option for it.
Use a different directory to install the libraries to, and write a
wrapper script, like
cv7:
#!/bin/bash
export LD_LIBRARY_PATH=/usr/lib/cv7/:$LD_LIBRARY_PATH
export WINEPREFIX=$HOME/.cv7/
export WINE_INI=.cv7rc
export WINE_INI_GLOBAL=/etc/cv7/config
exec /usr/lib/cv7/realcv7binary "$@"
Ciao, Marcus
