Ethereal-dev: Re: [Ethereal-dev] Current issues with MSVC build process andlibethereal

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: Joerg Mayer <jmayer@xxxxxxxxx>
Date: Sat, 6 Mar 2004 12:44:10 +0100
On Sat, Mar 06, 2004 at 10:46:37AM +1100, Ronnie Sahlberg wrote:
> What benefits would it have from a practical standpoint to have a shared
> library for ethereal?
> A lot of work but never any explanation on why we need it and what benefits
> it will provide.

Short term:
- much smaller executables:
  jmayer@madhatter:/usr/local/bin> ll ethereal tethereal dftest randpkt mergecap editcap
  -rwxr-xr-x    1 root     root      8909055 2004-02-29 20:31 dftest*
  -rwxr-xr-x    1 root     root       158200 2004-02-29 20:31 editcap*
  -rwxr-xr-x    1 root     root      9790923 2004-02-29 20:31 ethereal*
  -rwxr-xr-x    1 root     root       157885 2004-02-29 20:31 mergecap*
  -rwxr-xr-x    1 root     root       158864 2004-02-29 20:31 randpkt*
  -rwxr-xr-x    1 root     root      9150591 2004-02-29 20:31 tethereal*
 currently, knoppix only includes ethereal due to space reasons. That would
 be gone with shared libs.
- Less linking time (I'm still doing most of my work on a 128 MB machine)

Medium/Long term:
- cleaner code structure/API
- easier to use by other projects (think Packetyzer, NOT ClearSight)

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