Misc fixes and improvements for Requires and Requires.private
mclasen at redhat.com
Mon Dec 1 09:12:21 PST 2008
On Sun, 2008-11-30 at 16:15 +0100, Loïc Minier wrote:
> Hi there
> Could you please consider merging this branch?
Hmm, that link gives me an empty page...
> 196: Explain Libs.private versus Requires.private
> 195: Fix typo in man page and improve Requires.private section
> 194: Document --cflags-only-I in the man page
> 193: Allow for missing Requires in some cases
> 192: Add a test for missing Requires (failing)
> 191: Add an ignore_requires_private defaulting to TRUE
> 190: Cleanup logic when ignoring Requires
> 189: Check for missing .pc and Requires.private (failing)
> 188: Record pkg-config's output with LC_ALL=C set
> 187: Allow testing for error exit codes and output
> 186: Add .bzrignore
Thanks for working on this.
One thing that I think would help the whole pkgconfig confusion most,
IMO, would be if someone were to write a document that could be called
"Software development with pkg-config".
It would answer questions like
1) My program uses library x. What do I do ?
CFLAGS=`pkg-config --cflags x`
LIBS=`pkg-config --libs x`
(followed by a longer explanation of how this looks in autofoo)
2) My library z installs header files which include libx headers. What do I put
in my z.pc file ?
3) My library z uses libx internally, but does not expose libx datatypes in its
public api. What do I put in my z.pc file ?
More information about the pkg-config