public inbox for guile-gtk@sourceware.org
 help / color / mirror / Atom feed
From: Miroslav Silovic <silovic@zesoi.fer.hr>
To: Ariel Rios <jarios@usa.net>
Cc: guile-gtk@sourceware.cygnus.com
Subject: Re: Towards guile-gtk 0.18
Date: Mon, 25 Oct 1999 07:46:00 -0000	[thread overview]
Message-ID: <7eu2nfikc3.fsf@zesoi.fer.hr> (raw)
In-Reply-To: <19991024202010.8425.qmail@nwcst287.netaddress.usa.net>

Ariel Rios <jarios@usa.net> writes:

> Hi all--
> 
> Since the release of 0.17 I've been working towards having more Gtk+
> functions wrapped. Also, I've already included the changes required
> by guileGL to work.  I would like to know if any of you want a
> specific problem to be corrected for inclusion in the new version.

I've updated from CVS and compiled the new tree. The compilation is
taking forever, because of this:

-rw-r--r--   1 silovic  lss        469083 Oct 25 15:08 gtk-glue.c

I think that C file of this size is becoming an issue - adding
anything to gtk*.defs causes this to be recompiled - with another very
long wait.

This could be solved by splitting gtk.defs (and modifying
build-guile-gtk to allow it to export the glue generated by
define-object and define-enum declarations between multiple files).

-- 
How to eff the ineffable?

  reply	other threads:[~1999-10-25  7:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-24 13:14 Ariel Rios
1999-10-25  7:46 ` Miroslav Silovic [this message]
1999-10-25 10:55   ` Marius Vollmer
1999-10-25 14:45     ` Miroslav Silovic
1999-10-30 23:05     ` Jim Blandy
1999-10-31  4:34       ` Miroslav Silovic
1999-10-31  5:14       ` Marius Vollmer
1999-10-31  9:54         ` Keith Wright
1999-11-01  6:37           ` Jim Blandy
1999-11-02 21:42             ` Keith Wright
1999-11-13  7:42 ` Towards guile-gtk x.xx Daniel Skarda

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7eu2nfikc3.fsf@zesoi.fer.hr \
    --to=silovic@zesoi.fer.hr \
    --cc=guile-gtk@sourceware.cygnus.com \
    --cc=jarios@usa.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).