Ethereal-dev: RE: [Ethereal-dev] shared libraries

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

From: "Neulinger, Nathan R." <nneul@xxxxxxx>
Date: Mon, 19 Mar 2001 12:03:57 -0600
Whatever you do, please don't make it so it HAS to be a shared library.

-- Nathan

> -----Original Message-----
> From: Gilbert Ramirez [mailto:gilramir@xxxxxxxxx]
> Sent: Monday, March 19, 2001 9:52 AM
> To: Ed Warnicke
> Cc: ethereal-dev@xxxxxxxxxxxx
> Subject: Re: [Ethereal-dev] shared libraries
> 
> 
> Ed Warnicke wrote:
> > 
> > Is there a reason that libethereal, libdfilter, libftypes, 
> libwiretap,
> > and libui aren't being built and installed as shared libraries?
> > 
> > I know there is some mention of doing this in the epan directory,
> > but I was wondering if there was a good reason this hadn't 
> been done yet.
> > 
> > Ed
> 
> 
> There's no reason not to ship wiretap as a shared libary.
> Libethereal, however, still needs a little cleanup. There are some
> functions
> that it uses that are in the dissectors code. I tried it one time, but
> I don't remember exactly which functions. It had to do with address
> types
> used in packet.c that exist in the dissectors.
> 
> Hmm, maybe some better documentation on how to use wiretap would be
> good.
> Once its a shared library, there's a better chance that other projects
> will
> want to use it.
> 
> libdfilter and libftypes were meant to always be archives. When
> libethereal
> is a shared library, libftypes and libdfilter will be archives of PIC
> objects
> that are linked into libethereal.
> 
> Libui was also never meant to be a shared library.
> 
> --gilbert
> 
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev
>