[185] in The GTK GIMP ToolKit mailing list archive
[gtk-list] Gtk app build issues
daemon@ATHENA.MIT.EDU (Raph Levien)
Fri May 16 13:37:20 1997
Date: Fri, 16 May 1997 10:32:00 -0700 (PDT)
From: Raph Levien <raph@acm.org>
To: Otto Hammersmith <otto@redhat.com>
cc: gtk-list@redhat.com
In-Reply-To: <19970516032055.57369@redhat.com>
Resent-From: gtk-list@redhat.com
Reply-To: gtk-list@redhat.com
On Fri, 16 May 1997, Otto Hammersmith wrote:
> On Fri, May 16, 1997 at 08:25:20AM +0200, Sascha Ziemann wrote:
> > Can not compile it:
> >
> > szi@aibon:~/transfer/x/gzilla$ make
> > gcc -g -Wall -I/usr/ego/include -c gzilla.c -o gzilla.o
> > gzilla.c: In function `gzilla_con_input_handler':
> > gzilla.c:198: warning: implicit declaration of function `GTK_CHECK_CAST'
> > gzilla.c:198: parse error before `GzillaByteSink'
> > gzilla.c: In function `gzilla_con_query_handler':
> > gzilla.c:239: parse error before `GzillaByteSink'
> > make: *** [gzilla.o] Error 1
To compile 0.01 on your machine, you'll probably need -I/usr/ego/include
and -I/usr/ego/include/gtk .
[...]
> One thing that would be very nice, is if everyone would start
> standardizing on how to include gtk.h (as well as gdk.h and glib.h)...
>
> #include <gtk/gtk.h>
>
> Works best, I think... usually means less fiddling with -I options to
> the compiler. Especially if you use the RPMs for gtk on
> ftp.redhat.com:/pub/contrib... it puts the gtk include directory in
> /usr/include so there's no tweaking necessary. (BTW, there are RPMS in
> /pub/contrib... ignore the gimp-data one... 'tis from an older package
> built by someone else. :)
I agree, and have changed all of the #include directives to reflect this
suggestion. It now builds on my system with just -I/usr/local/include .
This is a major improvement. Thanks, Otto!
> In any case, I'm absolutely ecstatic that you released some code! The
> GzillaByteSink stuff is precisely what I needed...
I'm glad...
> Being 3:00am, I think I ought to stop rambling and get some sleep
> before I get back to work. :)
>
> Night all.
Stepping back for a moment, I've noticed that a lot of the problems
people are talking about on this list have to do with using simple.c as
the "hello world" template for building apps. However, simple.c has a lot
of things wrong with it:
+ #include "gtk.h" rather than #include <gtk/gtk.h>
+ signal handlers call gtk_exit (0) rather than gtk_main_quit ()
+ both signal handlers quit
+ no separate build process
I've put a tentative hello world example up at
http://www.levien.com/gimp/hello.html .
One thing this example is sorely lacking is an autoconf script. I have no
idea how to go about building one, but if anyone else here knows how and
would be willing to contribute, I'd be happy to put it on the page.
Raph
--
To unsubscribe: mail -s unsubscribe gtk-list-request@redhat.com < /dev/null
