Jeremy White wrote:
>
> Why do we have the -rpath option on by default?
>
> It creates a serious problem for us. Say we build
> a Winelib application for customer X. By default,
> that app is built with -rpath=/usr/lib/wine.
>
> However, that app relies on specific library versions
> of Wine. Even if I start my app with
> LD_LIBRARY_PATH=/opt/x/wine/lib, the X application
> will actually use the /usr/lib/wine shared objects.
>
> I would like to submit a patch to disable rpath
> by default, and add a '--enable-rpath[=DIR]' configure
> options. Objections?
we do have to use rpath so that we don't need to tweak
the LD_LIBRARY_PATH or /etc/ld.conf on any user configuration
since your request is specific (and using rpath seemed to be
agreed on latest Wine bottling discussion), I'd suggest doing
it the other way around:
- keep rpath as default
- add a configure.in option (--disable-rpath) to remove that
feature in case it's not wished
A+
--
---------------
Eric Pouech (http://perso.wanadoo.fr/eric.pouech/)
"The future will be better tomorrow", Vice President Dan Quayle
