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

[Peter Fritzsche]

Emilio Pozuelo Monfort wrote:
> On 24/05/10 11:07, Peter Fritzsche wrote:
> > So the cflags are untouched, but the libs are a lot cleaner for non
> > static compilations. Please change it to Require.private or give a good
> > reason not to do so
> 
> 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.

Best regards,
	Peter