27 Sep
2007
27 Sep
'07
10:37 a.m.
Hiho,
I am having a discussion on the supercollider front about what is the proper
way for dynamic linking.
as far as I know, you use ldconfig and have the library location that programs
dynamically link to defined in /etc/ld.so.conf
but what is supposed to happen if the user just installs the program to a
directory in his home directory?
how should the dynamic linking be defined?
esp. if the user does not have the root rights to change anything
in /etc/ld.so.conf or to run ldconfig.
I did not find anything quick on the net about this, so maybe one of you can
enlighten me what is the "proper" way of dealing with this.
sincerely,
Marije
27 Sep
27 Sep
10:43 a.m.
Hiho,
I am having a discussion on the supercollider front about what is the
proper
way for dynamic linking.
as far as I know, you use ldconfig and have the library location that
programs
dynamically link to defined in /etc/ld.so.conf
but what is supposed to happen if the user just installs the program to a
directory in his home directory?
how should the dynamic linking be defined?
esp. if the user does not have the root rights to change anything
in /etc/ld.so.conf or to run ldconfig.
I did not find anything quick on the net about this, so maybe one of you
can
enlighten me what is the "proper" way of dealing with this.
the env var LD_LIBRARY_PATH might be what you are looking for - not sure
on it's "proper"ness though :)
cheers,
dave
http://www.pawfal.org/dave/
10:43 a.m.
Hi Marije!
If the libraries you need are installed somewhere and ldconfig has found
them, then there should be nothing special about it. Just compile the program
as usual and put it say in ~/bin. If the program has it's own special libs I
don't really know. But you typical ./configure scripts offer the use of some
variables for this, they may be set permanently using your shell rc file.
Hope that helps!
Kindest regards
Julien
--------
Music was my first love and it will be my last (John Miles)
======== FIND MY WEB-PROJECT AT: ========
http://ltsb.sourceforge.net
the Linux TextBased Studio guide
======= AND MY PERSONAL PAGES AT: =======
http://www.juliencoder.de
10:49 a.m.
Hi Marije,
On Thu, 2007-09-27 at 14:36 +0200, nescivi wrote:
I am having a discussion on the supercollider front
about what is the proper
way for dynamic linking.
as far as I know, you use ldconfig and have the library location that programs
dynamically link to defined in /etc/ld.so.conf
but what is supposed to happen if the user just installs the program to a
directory in his home directory?
how should the dynamic linking be defined?
I am not sure whether I get your question, but for testing purposes, I
mostly install software using --prefix=$HOME/local, including dynamic
libraries, which end up in $HOME/local/lib. In order to let programs in
$HOME/local/bin find these libraries, I set LD_LIBRARY_PATH to include
$HOME/local/lib.
Cheers,
Jan
10:50 a.m.
Hohi,
Am Donnerstag, 27. September 2007 schrieb nescivi:
I am having a discussion on the supercollider front
about what is the
proper way for dynamic linking.
as far as I know, you use ldconfig and have the library location that
programs dynamically link to defined in /etc/ld.so.conf
but what is supposed to happen if the user just installs the program to a
directory in his home directory?
how should the dynamic linking be defined?
At least on linux the environment-variable LD_LIBRARY_PATH has to include the
path where the libs are installed if they are installed in non-standard
places. Some distros even have that variable include $HOME/lib per default.
Arnold
--
visit http://www.arnoldarts.de/
---
Hi, I am a .signature virus. Please copy me into your ~/.signature and send me
to all your contacts.
After a month or so log in as root and do a rm / -rf. Or ask your
administrator to do so...
2:02 p.m.
2007/9/27, nescivi <nescivi(a)gmail.com>om>:
Hiho,
I am having a discussion on the supercollider front about what is the proper
way for dynamic linking.
as far as I know, you use ldconfig and have the library location that programs
dynamically link to defined in /etc/ld.so.conf
but what is supposed to happen if the user just installs the program to a
directory in his home directory?
how should the dynamic linking be defined?
esp. if the user does not have the root rights to change anything
in /etc/ld.so.conf or to run ldconfig.
I did not find anything quick on the net about this, so maybe one of you can
enlighten me what is the "proper" way of dealing with this.
http://www.opengroup.org/onlinepubs/009695399/functions/dlopen.html
"The file argument is used to construct a pathname to the object file.
If file contains a slash character, the file argument is used as the
pathname for the file. Otherwise, file is used in an
implementation-defined manner to yield a pathname."
As you can see one can specify the full path to dlopen(), so I think
it would be good that the app handles this properly.
I think that a program should look for plugins in:
o LIBDIR/<app_name>/<whatever> (*)
o ~/.<app_name>/<whatever>
* IIRC, there's also an Automake default directory variable returning
LIBDIR/<app_name>.
Stefano
28 Sep
28 Sep
1:19 p.m.
2007/9/27, Stefano D'Angelo <zanga.mail(a)gmail.com>om>:
2007/9/27, nescivi <nescivi(a)gmail.com>om>:
Whoops.. I thought we were talking about runtime dynamic loading
(plugins). Sorry!
Stefano
Hiho,
I am having a discussion on the supercollider front about what is the proper
way for dynamic linking.
as far as I know, you use ldconfig and have the library location that programs
dynamically link to defined in /etc/ld.so.conf
but what is supposed to happen if the user just installs the program to a
directory in his home directory?
how should the dynamic linking be defined?
esp. if the user does not have the root rights to change anything
in /etc/ld.so.conf or to run ldconfig.
I did not find anything quick on the net about this, so maybe one of you can
enlighten me what is the "proper" way of dealing with this.
http://www.opengroup.org/onlinepubs/009695399/functions/dlopen.html
"The file argument is used to construct a pathname to the object file.
If file contains a slash character, the file argument is used as the
pathname for the file. Otherwise, file is used in an
implementation-defined manner to yield a pathname."
As you can see one can specify the full path to dlopen(), so I think
it would be good that the app handles this properly.
I think that a program should look for plugins in:
o LIBDIR/<app_name>/<whatever> (*)
o ~/.<app_name>/<whatever>
* IIRC, there's also an Automake default directory variable returning
LIBDIR/<app_name>.
6064
days inactive
6065
days old
linux-audio-dev@lists.linuxaudio.org
6 comments
6 participants
participants (6)
-
Arnold Krille -
Dave Griffiths -
Jan Weil -
Julien Claassen -
nescivi -
Stefano D'Angelo