This is the mail archive of the mailing list for the eCos project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: vnc and lwip

On Fri, 28 May 2004 20:16:52 +0100
Jonathan Larmour <> wrote:

> Andrew Lunn wrote:
> > On Fri, May 28, 2004 at 06:33:55PM +0300, Jani Monoses wrote:
> > 
> >>Since lwip has a network.h header for compatibility with the other stacks
> >>this can be applied.Will do so if nobody objects.
> Excuse my unfamiliarity but shouldn't lwip use the "standard" header 
> locations for its API headers? Or is this something in the upstream main 
> lwip distribution.

lwip uses its own header names because it started out as a tcp/ip library to
be linked with specific apps not as a a 'standard' tpc/sockets/dns stack.
The sockets code was only added some time after it was already usable.
But with it now being in ecos there's more sense in making it support a
standard interface because now porting to ecos/lwip makes sense too, as
opposed to'building/hacking lwip into my project'.
When/if the bsd stacks won't need network.h lwip can be modified to to use
standard headers. Right now I want to keep the lwip vs bsd_net ifdefs as few
as possible.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]