Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Ethereal-dev: Re: [Ethereal-dev] Next step in build process cleanup

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

From: Ed Warnicke <hagbard@xxxxxxxxxxxxxxxxxxx>
Date: Tue, 25 Mar 2003 16:36:52 -0500
Joerg,
   I'd rather that
A) Collapse configure and epan/configure into one (and maybe
       wiretap/configure)
not occur for the following reason:
I'd like to see epan and wiretap independently distributable at some
point so that they can be used by applications other than
ethereal and tethereal.  I suspect there are others here who share
similar ambitions.  Collapsing epan/configure and wiretap/configure
into configure moves us further from this goal.

Just my two cents :)

Ed
Joerg Mayer wrote:

On Tue, Mar 25, 2003 at 01:00:44PM -0800, Guy Harris wrote:
Well, it appears to work on Solaris 8, although I'm still seeing the

	libtool: link: warning: `AC_LIBTOOL_DLOPEN' not used.  Assuming
	    no dlopen support.

messages when it links Ethereal and Tethereal - we *are* using
AC_LIBTOOL_DLOPEN in the top-level configure.in, so I'm not entirely
sure what the problem is.

That one is still on my todo list - here's it in full (not long but a bit
of work left :)

a) Fix dlopen support to work again on current Suse etc systems.
b) Don't add /usr/local/include to the include path, if the compiler
  already searches there (I don't like those gcc warnings).

A) Collapse configure and epan/configure into one (and maybe
 wiretap/configure)
B) Move dissectors and other stuff into their own epan subdir
C) Get others to properly seperate gui functionality from otherwise
 sharable files :)

I don't yet know how to do a) or b) As far as a) is concerned: I have read
the autoconf and automake and libtool info pages and have done some
experiments but without success. Next step will be to update all three
tools to the newest version and see if that helps. If not, I'll just go
and ask on the appropriate mailing list for help. If anyone knows how
to do a) or b): Just do it  :-)
A)-C) are up for discussion: I won't commit anything without sending in
patches for review first (maybe I'll do B in a branch of it's own).

Ciao
        Jï¿œrg

--
Joerg Mayer                                            <jmayer@xxxxxxxxx>
We are stuck with technology when what we really want ist just stuff that
works. Some say that should read Microsoft instead of technology.

_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev