[1879] in Kerberos_V5_Development
Re: On libdb and shared libraries....
daemon@ATHENA.MIT.EDU (Barry Jaspan)
Sun Oct 27 11:27:46 1996
Date: Sun, 27 Oct 1996 16:27:26 GMT
From: "Barry Jaspan" <bjaspan@MIT.EDU>
To: epeisach@MIT.EDU
Cc: krbdev@MIT.EDU
In-Reply-To: <9610270430.AA11903@kangaroo.mit.edu> (epeisach@MIT.EDU)
You do not list what I consider the right solution among the options.
We should never use -L for libs in the build tree. All libraries that
we build should be specified via explicit paths; only system libraries
should be linked with -l (note that we already maintain that info in
DEPLIBS). This has several advantages. One, you eliminate problems
with the -l search path as you are describing. Two, on OS's that put
all -L options into LD_LIBRARY_PATHS (or whatever), you don't end up
with binaries that search non-existant relative paths at runtime.
(Three, if you are using gmake, LIBS can be used as a dependency,
instead of having to maintain DEPLIBS separately, but that only works
with gmake).
Barry
