This is the mail archive of the
guile-gtk@sources.redhat.com
mailing list for the Guile project.
Re: Currnet CVS fails to configure - the patch
- To: Ariel Rios <ariel at arcavia dot com>
- Subject: Re: Currnet CVS fails to configure - the patch
- From: Marius Vollmer <mvo at zagadka dot ping dot de>
- Date: 13 Jan 2001 13:03:14 +0100
- Cc: Martin Baulig <martin at home-of-linux dot org>, guile-gtk at sourceware dot cygnus dot com
- References: <Pine.LNX.4.10.10101061756310.1116-100000@soleil.gnome.org>
Ariel Rios <ariel@arcavia.com> writes:
> > If we need all this complexity for Gtk 2.0, we should make a
> > branch for this in guile-gtk.
>
> We depende on a new Gtk 1.2 release but I am starting to wonder if
> Owen / Havoc will ever do one.
Ok, we need to make some progress on this.
There are two issues: generating the build scripts from their sources
(i.e. configure.in -> configure), and running the build scripts from a
tar ball (i.e. running configure). Let's call the people who do the
first thing `developers', and the rest `users'.
The ideal thing would be to have a single guile-gtk package for all
versions of Gtk+. We should try hard to achieve this. (That is, no
branch.)
It is OK when developers need to get extra stuff like gnome-common and
pkg-config even if they are not using Gtk+2. It is not OK that users
need these packages if they are not using Gtk+2.
Right now, it is more important that guile-gtk works for the 1.2.x
branch of Gtk+ than that it works for the upcoming 2.0. So the first
thing we need to do is to make sure that the generated configure
script runs on a system that does not have gnome-common or pkg-config
or glib.pc, etc.
Essentially, configure should be reverted to its old behaviour when
pkg-config is not found, and just use gtk-config.
Is this OK with everyone?