[RFC] Use glib-2.0 exclusively

Tollef Fog Heen tfheen at err.no
Thu Aug 26 12:20:10 PDT 2010


]] Enrico Weigelt 

| * Paul Bender <pebender at san.rr.com> schrieb:
| 
| > However, I cannot see any reason that pkg-config could 
| > not do the same thing with glib2 (and its dependencies: zlib). 
| 
| Is there any technical reason to move to glib2 ?
| What does it have that's _needed_ and the current in-tree glib1
| does not have ?

A working option parser implementation, for instance.  Less code to
maintain.

| Do you really want to exchange an long matured copy of glib1 by a new
| complex magic for building an separate external glib2 ?

I wouldn't consider

PKG_CONFIG=/bin/true PCRE_LIBS=$(pcre-config --libs)
PCRE_CFLAGS=$(pcre-config --cflags) ./configure

to build glib particularly complex or magic.

| Oh, BTW, already mentioned: glib2 is not crosscompilable.

And as I said, people have yet to come up with an use case for needing
pkg-config cross-compiled.  Either you can just build for your build
architecture (but targetting your target, wrt where it should look for
.pc files), or you can just build on the target.  If the latter is a
problem, you probably don't need pkg-config on there anyway.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are


More information about the pkg-config mailing list