28 Sep
2007
28 Sep
'07
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>.