[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: why do some libs have pc file, and some don't ?



On Sun, 29 Mar 2009 13:51:51 +0200
Jérémy Lal <jerry@edagames.com> wrote:

> for example, libsoup-dev has /usr/lib/pkgconfig/libsoup-2.4.pc
> while liburiparser-dev don't.
> how come ?

Depends whether upstream support pkgconfig for configuration support in
builds using the library. The .pc file consists of the metadata that
pkgconfig needs to tell that a particular version has been installed,
which libraries it needs to add to the list for linking the final
executables and various other bits of data.

Libraries with -dev packages not using pkgconfig need to provide some
other means of providing this data - some use their own config scripts.
The problem is that those rarely support situations like
cross-building. pkgconfig isn't perfect (see the recent thread on
spurious dependencies from Gtk) but it is a lot more portable than
bespoke hacks.

-- 


Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/

Attachment: pgpFiV9d9f6VP.pgp
Description: PGP signature


Reply to: