On Mon, Aug 19, 2002 at 01:35:41PM -0700, 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.
Sure. The above patch was just a test to find out how much work is required
at the source level. I agree that users (and developers) should have the
choice of which gui (if any) they want to use.
> Another possibility might be to have autogen.sh build
> configure.in and the like based on whether *it* detected various
> packages being present.
I'll have a look at something like that unless someone beats me to it.
The KDE people have a configure.in.in, maybe that is their solution to
this problem, maybe it's the solution to something completely different.
With a little luck I'll meet Dirk tomorrow and ask him a few questions
why they did it and how.
Ciao
J�rg
--
Joerg Mayer <[EMAIL PROTECTED]>
I found out that "pro" means "instead of" (as in proconsul). Now I know
what proactive means.
