On Jan 26, 2004, at 8:29 PM, Bill Northcott wrote:
From: Rich Cook <email@hidden>
Hmmm... How is placing a useful library in a standard location like
/usr/local/lib "pollution?"
/usr/local/lib is only marginally different to /sw/lib. If either is
in the default ld/dyld search paths or I use -L/usr/local/lib in a
link command, I am immediately condemned to link all the
Fink/whatever
stuff that has been installed, whether I want it or not. That is
what
I mean by pollution. Obviously the same applies to headers at
compile
time.
You are just incorrect here. -L/usr/local/lib does not link
*ANYTHING*
in, it simply adds /usr/local/lib to the search paths for libs you
explicitly request with -lname.
Also, there is an important difference between /sw/lib and
/usr/local/lib that seems to escape your attention: everybody else
knows about /usr/local/lib, whereas /sw/lib is a bit odd. Following
convention can be useful when porting codes across multiple platforms.
