Policy for adding library to system?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I am just looking for a good method to add some libraries to my system.
Let's assume we have the following situation:
The directory /usr/local/foo/include contains a lot of ugly headerfiles and
/usr/local/foo/lib some (static) libraries. /usr/local, by the way, is a
NFS-filesystem for the cluster. Now, I want that my users can compile their
program without adding long -L and -I options when they use gcc.
Now I see the following possibilities:
1) Copy or link the files to /usr/lib on every machine. Very ugly, isn't it?
2) I set LD_LIBRARY_PATH and C_INCLUDE_PATH in /etc/bash.bashrc (or
something like that).
Isn't there any better way to tell the system that there are some new
libraries? A global configuration file, which coontains all include and
library directories?
Thanks,
Alexander
- --
Alexander Schinner @ mailto://alexander.schinner@itp.uni-frankfurt.de
@ http://octopus.th.physik.uni-frankfurt.de/~schinner
Supercomputing @ http://tina.nat.uni-magdeburg.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE7emJVqvrueRL0OOoRAr6NAKC+YFaz7d/denvDwNAJXGzYpIv9HgCgiYuX
D94qwE3LAw8Dqr6sKEazdmI=
=l+S4
-----END PGP SIGNATURE-----
Reply to: