On Mon, 10 Dec 2007 22:10:49 +0100 Pierre Habouzit <madcoder@debian.org> wrote: > > > > That is supported in pkg-config, but no upstream I've ever met seems to > > > > understand it yet. > > > > > > Ah, I see. I overlooked the --static flag to pkg-config because (case > > > in point) "pkg-config --libs gtk+-2.0" only misses seven of the > > > libraries that the --static version uses. I would guess this is > > > because "Requires.private" is not mentioned in the pkg-config man > > > page. At least on my system, Libs.private seems to be used correctly > > > by most or all .pc files, but Requires.private use is spotty. > > > > The flaw in the documentation is surely the part to blame here. > > Requires.Private works but is not mentioned anywhere. Neither is the --static > > option in the SYNOPSIS part of the man page. > > Not many use undocumented stuff. > > You're kidding ? If someone that produces libraries stop at the SYNOPSIS > section while reading documentation, he's a moron. The pkg-config tool > has a very concise documentation that says it all, --static is > documented in the OPTIONS section, and Requires, Libs, Libs.private in > METADATA FILE SYNTAX where due. Calling it undocumented is just either > bad faith or well, I can't see what else it can be in fact. What *is* missing is documentation of Requires.private: -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
Attachment:
pgp_ez0wWqFvf.pgp
Description: PGP signature