Subject: [ecasound] library locations
From: Kai Vehmanen (email@example.com)
Date: Tue Aug 29 2000 - 23:22:17 EEST
Shortly put, where (and how) should ecasound libraries be installed? I've
been trying out various alternatives, but this seems to be quite a nasty
problem. Basicly when a dynamically linked program is loaded, there are
three ways to find the required libraries:
1. Directory is specified with LD_PRELOAD, etc variables.
2. Directory is listed in /etc/ld.so.conf
3. Directory is hard-coded with ld's -rpath option.
All approaches have problems. If I compile the source myself, ecasound
has a hardcoded path to /usr/local/lib, so libraries are found even if
you don't have /usr/local/lib in your /etc/ld.so.conf.
But binary packages built elsewhere are a different thing. Especially with
rpms, this is a major problem, as they are built in temporaray directories
(to make the rpm's relocatable). Then the hard-coded directories are wrong
(for instance: /tmp/ecasound-build/usr/local/lib).
Now, I'd like to put all libraries under /usr/local/lib/ecasound, but as
you can see, this is a bit problematic. Either we lose relocatability, or
we add complexity to the install routines.
PS; this doesn't really affect plugins. As for now, they will be kept in
-- . http://www.eca.cx ... [ audio software for linux ] /\ . . http://www.eca.cx/aivastus ... [ aivastus net radio ] /\ . . http://www.eca.cx/sculpscape [ my armchair-tunes mp3/ra/wav ]
-- To unsubscribe send message 'unsubscribe' in the body of the message to <firstname.lastname@example.org>.
This archive was generated by hypermail 2b28 : Wed Aug 30 2000 - 00:01:53 EEST