Bug#582860: [libgtk2.0-dev] pkg-config requires too many libraries

Josselin Mouette joss at debian.org
Tue May 25 06:39:48 UTC 2010


Le lundi 24 mai 2010 à 11:49 +0200, Peter Fritzsche a écrit :
> Emilio Pozuelo Monfort wrote:
> > Even though I'd really like to do that, I'm not still convinced we can do
> > it in GTK+. Since GTK+ exports APIs of those libraries in its public
> > headers, applications linking to GTK+ should link to those libraries too.
> > Or do you say cflags would be enough, but not libs?
> 
> If they are using other libraries then they must use their pkg-config 
> anyway... otherwise they are broken. If the programs just use some structs or 
> other things which are declared in their header then the cflags just looks 
> like before and nothing has changed for them.
> 
> Or do you mean that there is a gtk_blablubfoo() which just is a define or 
> static inline function in their headers which uses glib_foobar()? It would 
> make gtk+-2.0 an evil library and prevent Requires.private.

For example some GTK+ functions return structures or types that are
defined in Glib or Pango.

-- 
 .''`.      Josselin Mouette
: :' :
`. `'   “A handshake with whitnesses is the same
  `-     as a signed contact.”  -- Jörg Schilling







More information about the pkg-gnome-maintainers mailing list