Hi ULFL,
Yeah, I appreciate that the ethereal developers have lots more
important work to do. Ethereal is a great software!!!
Would it be worth fixing the build problems first, and then tackling
problems as they arise. For example you mention that libethereal does
not support having multiple instances of everything. Do you mean that
libethereal is not multi-threaded? or that all dissection trees share
common static memory?
We could say that libethereal is not multi-threaded at this stage,
and then fix bugs as they are found in static memory allocation.
I think I have a way to work around the build deficiencies, but it is
an ugly hack (tm). I can do an ldd on the ethereal/tethereal binary
and just link all those libraries into my binary as well.
Would it be worth having a look at the libethereal build process to
see if I can easily fix this for inclusion into cvs?
Michael.
On Fri, May 27, 2005 at 04:12:47PM +0200, Ulf Lamping wrote:
> Hi Micheal.
>
> libethereal in it's current state isn't meant to be used by other
> programs than the Ethereal package itself, as this would require a lot
> more effort.
>
> The main purpose was to simply save code space as both ethereal and
> tethereal uses a whole lot of identical code (that's how I
> understand/remember it).
>
> Someone else might correct me, but there are currently no attempts to
> bring libethereal into a state where other programs (like your's) can
> conveniently use libethereal. This would require more work, like making
> it possible to keep multi instances of everything and ...
>
> I do agree that this goal would be useful. But believe me, the Ethereal
> developers have still a lot of other work to do ;-)
>
> Regards, ULFL
>
> _______________________________________________
> Ethereal-dev mailing list
> Ethereal-dev@xxxxxxxxxxxx
> http://www.ethereal.com/mailman/listinfo/ethereal-dev