tags 349318 + fixed-upstream On Sun, Jan 22, 2006 at 02:44:28AM -0800, Steve Langasek wrote: > So, I suppose most of you have read > <http://lists.debian.org/debian-devel-announce/2005/11/msg00016.html> about > problems with packages depending on libraries that they don't use, > particularly as relates to a potential libfreetype transition. One library > that currently exposes freetype (and other libs) in its pkg-config .pc file, > but shouldn't, is libxft. > > Please consider (and forward upstream) the attached patch which moves all of > the library dependencies of libxft into the Libs.private variable in xft.pc, > so that they aren't used on Debian except for static linking. I have not > touched the 'Requires' field; even though packages which link to libXft > should not need to link to libfontconfig, the pkg-config 'Requires' field > controls both CPPFLAGS and LDFLAGS, and Xft includes fontconfig headers -- > unfortunately the pkg-config maintainer has not been convinced that CPPFLAGS > from Requires.private should be propagated, despite the fact that there are > many examples of this scenario in Debian... (this is bug #340904, for those > who care.) > > FWIW, since September 2003 FreeType has supported pkg-config; however, I > wouldn't recommend that Xft use pkg-config dependencies for libfreetype > unless this Requires.private CPPFLAGS issue is resolved. :/ > > Oh, also, there seems to be a pre-existing bug in this .pc file, in that > -lX11 is specified for static linking, but -L/usr/X11R6/lib is not...
This has already been fixed in the modular tree (/cvs/xorg/lib, as opposed to /cvs/xlibs). But I guess the CPPFLAGS scenario remains. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]