Re: static library dependencies

[Howard Chu <hyc at highlandsun dot com>]

Ian Lance Taylor wrote:
> That could be done, and I believe it could even be done in a backward
> compatible manner, but it would lead to the same set of issues that
> arise with shared libraries.  Because archives can move around and be
> renamed, you need to use a search path.

(Sorry for the late reply, your msg went into my spam trap for some reason.)

Mike Frysinger wrote:
> sounds like over engineering when practical solutions already exist.  use
> libtool and/or pkg-config.  both have been working for years for people.
> -mike

Hm, you can criticize over-engineering and then mention libtool in the next 
sentence?

I find that pkg-config tends to misbehave when you have stuff in /usr and in 
/usr/local, it often says a package is missing even though it's present. And 
ultimately it's a lot more plumbing to maintain, and it's clumsy because the 
state info is kept in a separate location from the actual packages. Likewise 
libtool .la files are clumsy and the standard linker doesn't know about them. 
These (libtool/pkg-config) are both kludges, not solutions.

--
  -- Howard Chu
  CTO, Symas Corp.           http://www.symas.com
  Director, Highland Sun     http://highlandsun.com/hyc/
  Chief Architect, OpenLDAP  http://www.openldap.org/project/