Ethereal-dev: Re: [Ethereal-dev] Compiling with glib2/gtk+2 (not yet) (with attach)

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Guy Harris <gharris@xxxxxxxxx>
Date: Mon, 19 Aug 2002 13:35:41 -0700
On Sat, Aug 17, 2002 at 11:01:29PM +0200, Joerg Mayer wrote:
>  # Checks for glib first, or gtk+ if not present
> -AM_PATH_GLIB(1.1.0, CFLAGS="$CFLAGS $GLIB_CFLAGS" LIBS="$LIBS $GLIB_LIBS", , gmodule)
> +AM_PATH_GLIB_2_0(2.0.0, CFLAGS="$CFLAGS $GLIB_CFLAGS" LIBS="$LIBS $GLIB_LIBS", , gmodule)

One problem with that is that it'd require GLib 2.x (and you'd probably
have to go for GTK+ 2.x as well) in order to build Ethereal at all; 2.x
is probably new enough that we don't want to require it just to use
Ethereal or build the release.

Even if we fix that (either by having a "--with" option to choose which
version of GLib and GTK+ to use, or by having it look for both and
prefer 2.x, or by having it look for both and prefer 2.x but allow you
to override that with a "--with" option; I prefer the third of those),
another problem with that is that it'll mean that you'd need to have
GLib 2.x installed in order to build from CVS.

I think I once tried to see if I could use M4 ifdefs to arrange that if
a given macro wasn't defined it wouldn't be used, but, as I remember,
that didn't work.  Another possibility might be to have autogen.sh build
configure.in and the like based on whether *it* detected various
packages being present.

(As I remember, Michael Tuexen complained a while ago about not being
able to build Ethereal from CVS on a platform that didn't have GTK+
installed - all he cared about for that machine was Tethereal - and I'd
prefer to require *fewer* things for CVS builds, not *more* things.)

A scheme such as that might come in handy if, for example, we add
support for other toolkits.