static library dependencies

[Mike Frysinger]

On Friday 19 March 2010 18:24:49 Howard Chu wrote:
> 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.
> 
> Hm, you can criticize over-engineering and then mention libtool in the next
> sentence?

i find that most people who criticize libtool dont understand it and instead 
try to develop yet another method for doing what it does, except they lack all 
of the solutions that libtool incorporates

> 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.

sounds like you're trying to augment your host system with random other 
packages without informing the tools where to find additional things.  i.e. if 
your system is misconfigured, fix that.  tell pkg-config where to find all of 
the random .pc files you're installing in non-standard locations.

> 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.

"separate location" huh ?  are you suggesting you dump all the random files a 
package installs into one directory ?  things are separated into different 
logical directories as designed.

> Likewise libtool .la files are clumsy and the standard
> linker doesn't know about them. These (libtool/pkg-config) are both
> kludges, not solutions.

they're both portable solutions with a much bigger picture in mind than your 
narrow focus here.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <https://sourceware.org/pipermail/binutils/attachments/20100320/90028e13/attachment.sig>