Re: Shared library defines a RPATH
On Sat, 27 Jul 2002, Mikael Hedin wrote:
> all use 2 shared libs in the same dir. They use rpath, and I think
> it's appropriate.
No, it is not. We don't want rpath because we want our libraries to be
"relocatable" file-system wise. So, there are absolutely no exceptions.
Plugins are another matter: since they do not need to be relocatable
file-system wise, we accept rpath there (but it IS much better to just use
the damn full path in dlopen() ).
If upstream uses a poor naming scheme for their shared libs, and those libs
won't be ever used by anything else than the same set of programs, prefix
them with the package name, or something like that.
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org