Ethereal-dev: Re: [Ethereal-dev] Compiling with glib2/gtk+2 (not yet) (with attach)
Dear all,
see my comments below.
Best regards
Michael
On Monday, Aug 19, 2002, at 22:35 Europe/Berlin, Guy Harris wrote:
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.)
I also vote for fewer is better then more.
On Mac OS X 10.2 you can compile tethereal (after installing the glib)
but 'out of the box' there is no XServer installed. I think in
such a setup tethereal is very helpful. If the user also wants
ethereal, he has to install an XServer (with the libraries and sources,
which means the XFree86 release) and then can easily build ethereal.
But this should not be required.
A scheme such as that might come in handy if, for example, we add
support for other toolkits.
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev
