On Wed, Aug 6, 2008 at 1:20 PM, Peter TB Brett <[EMAIL PROTECTED]> wrote:
> On Wednesday 06 August 2008 11:18:21 Bernd Jendrissek wrote:
>> "The compiler has to chow through more than a megabyte of input
>> for each gEDA source file it compiles."
[snip]
> I do want to PURGE Gtk/Gdk from libgeda, though. There really is no good
> reason for us having to link libgeda against it. *scowl* The Gtk headers are
> a heck of a lot larger than the GLib ones! This actually irritates me enough
> that I might do something about it.

When I last looked at it, the bulk of the C preprocessor output
actually comes from libguile, with the GTK+ stack somewhat behind.

As far as I can tell the only real need for anything higher in the
stack than GLib is the PICTURE stuff.  Making that an opaque type is
not enough though, as gschem wants access to the GdkPixbuf, so that
token has to appear in <libgeda/prototype.h>.  One more reason why I
consider typedef to be harmful - otherwise we could just
forward-declare "struct GdkPixbuf;" and only pull in <gtk/gtk.h> in
gschem.  I'd be quite uneasy about doing that trick with too much
knowledge of GTK+ internals.  But it's an idea... perhaps a local
patch for my antedeluvian PC <evil grin>.


_______________________________________________
geda-dev mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev

Reply via email to