Le Monday 10 December 2007 20:03:50 Pierre Habouzit, vous avez écrit :
> > Perhaps the "absurd and wrong" part is that pkg-config does not
> > provide a way to distinguish between use cases, and that the name for
>
> Wrong, please read pkg-config(1) and think again.
>
> $ pkg-config tokyocabinet --libs
> -ltokyocabinet
> $ pkg-config tokyocabinet --libs --static
> -ltokyocabinet -lz -lpthread -lm -lc
> $ grep Libs /usr/lib/pkgconfig/tokyocabinet.pc
> Libs: -L${libdir} -ltokyocabinet
> Libs.private: -lz -lpthread -lm -lc
>
>
> pkg-config *is* perfectly suited for that matter actually, and
> "broken" pkgconfig upstreams are this trivial to fix. My upstream for
> tokyocabinet uses in a tokyocabinet.pc.in:
> Libs: -L${libdir} -ltokyocabinet @LIBS@
> the fix is just to put the @LIBS@ onto Libs.private and be done with it.
> Upstreams using pkg-config are actually the first _easy_ targets to fix
> the dependency issues _they_ generate in others binaries. And there is
> no reason no to fix those when it's easy to do so.
Right, so now I now how to fix #395185 .. Seems I lacked some knowledge about
pkg-config :-)
Romain
