wrong gnutls.pc

[Vincent Torri]

On Sat, Feb 27, 2010 at 8:06 PM, Andreas Metzler <
ametzler at downhill.at.eu.org> wrote:

> > > If it exists, 'libtasn1' must appear in the Requires.private field
> > > (or Requires field if you support pkg-config 0.22).
>
> As far as my testing runs Requires.private works perfectly fine with
> pkg-config 0.22, it is just not documented.
>
>
missing '<' : pkg-config < 0.22

>
>
>
> > sure, but having libtasn1 in Requires.private instead of having -ltasn1
> in
> > Libs.private is different. pkg-config takes care of the possible
> > dependencies with the Requires.private field. Look at pkg-config
> > documentation. By doing what you do, you can broke linking with future
> > versions of libtasn1 if it has dependencies.
>
> So the major upside of Requires.private over Libs.private is that
> pkg-config could recourse over the required libraries dependencies?
>
> pkg-config(1) is rather short, it basically just says
>
> "[Libs.private:] This differs from Requires.private: in that
> it references libraries that do not have package files installed."
>
> without saying why Requires.private /should/ be used for pkg-config
> using libraries.
>

1) If the dep is a lib that has a .pc then put it in Requires.private (like
libtasn1)
2) if the dep does not have one, put -lfoo in Libs.private (like libgcrypt
or zlib)

that's the rules to follow.

Vincent Torri
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20100228/190eb3b1/attachment.htm>