From: John Kodis <kodis@mail630.gsfc.nasa.gov>
To: "Neil W. Van Dyke" <nwv@acm.org>
Cc: Ariel Rios <ariel@linuxppc.org>,
guile-devel@gnu.org, guile-gtk@sourceware.cygnus.com
Subject: Re: suggestions for Guile wrt GTK and Gnome support
Date: Tue, 24 Jul 2001 08:26:00 -0000 [thread overview]
Message-ID: <20010724112604.A27715@tux.gsfc.nasa.gov> (raw)
In-Reply-To: <15197.28379.594775.931898@winona.neilvandyke.org>
On Tue, Jul 24, 2001 at 08:49:31AM -0400, Neil W. Van Dyke wrote:
> I'm guessing that more often than not, people who were open to
> becoming Guile application hackers get the
> not-entirely-fair-but-understandable impression that Guile is not
> ready for prime-time.
This has been my experience. I'd love to make more extensive use of
guile and its Gnome and Gtk bindings, but frequently run into problems
getting a working installation set up.
I just tried this today. The problems I encountered were:
- I could find no guile-related package in
ftp.gnome.org:/pub/GNOME/stable/sources.
- I tried to follow a previous suggestion and get the latest CVS
modules. I checked out a copy of guile-gtk and gnome-guile, but was
unable to build either. The autogen.sh script couldn't find
gnome-autogen.sh and failed.
- From what I remember, the last time that I was able to build these
packages, I was unable to run any of the programs in the gnome
examples directory -- they would all fail with an error to the
effect that the "gtk gtk" module could not be found.
I don't imagine that any of these problems would be difficult to
overcome, but there's no way of knowing how many of these types of
minor difficulties I'd run into before I had a working gnome-guile
system. Faced with this uncertainty, I tend to just fire up glade and
use C instead. It's less elegent, but I know I can get it to work.
--
John Kodis <kodis@acm.org>
Phone: 301-286-7376
next prev parent reply other threads:[~2001-07-24 8:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <15196.20913.8186.886002@winona.neilvandyke.org>
2001-07-23 22:12 ` Ariel Rios
2001-07-23 23:34 ` Martin Grabmueller
2001-07-24 2:37 ` Thien-Thi Nguyen
2001-07-24 5:51 ` Neil W. Van Dyke
2001-07-24 8:26 ` John Kodis [this message]
2001-07-24 6:29 ` Dale P. Smith
[not found] <200107231740.KAA10213@twinge.hungry.com>
2001-07-23 22:14 ` Ariel Rios
2001-07-23 22:50 ` Seth Alves
2001-07-26 1:59 ` Thien-Thi Nguyen
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=20010724112604.A27715@tux.gsfc.nasa.gov \
--to=kodis@mail630.gsfc.nasa.gov \
--cc=ariel@linuxppc.org \
--cc=guile-devel@gnu.org \
--cc=guile-gtk@sourceware.cygnus.com \
--cc=nwv@acm.org \
/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).