Re: libgtk-dev bug?
On Wed, Jul 29, 1998 at 04:40:14PM +0100, Enrique Zanardi wrote:
> libgtk-dev provides two glib header files: /usr/include/glib.h and
> /usr/lib/glib/include/glibconfig.h
>
> glib.h has a "#include <glibconfig.h>" line.
>
> Is there any reason not to move glibconfig.h to /usr/include , removing
> /usr/lib/glib/include (glibconfig.h is the only file there), and the need
> to explicitly declare -I/usr/lib/glib/include when compiling GTK-using
> code?
glibconfig.h is supposed to contain system-specific stuff, so it goes
under the /usr/lib hierarchy (/usr/include should be nfs-exportable
to multiple architectures).
> I know the developers should use "gtk-config --cflags" when compiliing their
> GTK-using code, but as currently "gtk-config --cflags" output is just
> "-I/usr/lib/glib/include -I/usr/X11R6/include", it looks like overkill,
> and many upstream developers don't use it. I was bitten by this one when
> compiling SANE 0.74.
It's a bug in the upstream makefiles.
This feature is essential to support easy compilation of gtk+
programs (maybe for different versions of gtk+) now and when themes
support will come.
What is easier than gcc stuff.c -o stuff `gtk-config --cflags --libs`?
Look, ma! No autoconf:-)
lupus
--
"The number of UNIX installations has grown to 10, with more expected."
- _The UNIX Programmer's Manual_, Second Edition, June, 1972.
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: