Re: [lwip-users] Lwip Socket Library

[Kieran Mansley]

On Tue, 2006-07-11 at 10:07 +0200, Christiaan Simons wrote:
> Hi Kieran,
> 
> Sorry for breaking in on this,

Not at all - very helpful.

> > On Mon, 2006-07-10 at 15:31 -0700, e8h3wy wrote:
> > > Hi All. Could someone please help me with using the socket API shared
> lib -
> > > liblwip.so? I tried to compile a small echo server written using lwip
> socket
> > > API (lwip_socket, lwip_bind etc), but I get some missing symbols. What
> other
> > > objects should I include in the build, to satisfy the loader? Any hints
> > > appreciated.
> >
> > Hmm, from the symbols you are missing it seems to be an odd collection
> > of sys and raw API stuff.  The raw API stuff is a bit confusing - as far
> > as I remember (it was nearly four years ago I wrote this example lib
> > project) it didn't support the raw API.
> 
> Raw API shouldn't be too confusing anymore, some missing
> details are now documented in doc/rawapi.txt.
> Example usage is in contrib/ports/unix/proj/minimal.
> It should be very clear now, I hope ...

Apologies, I didn't mean that the raw API was confusing, but that the
presence of the missing raw API symbols in the library was confusing!

> >  Are you making calls to the raw
> > API from your es.c code?  If you need it I suppose you could add raw.c
> > to the APIFILES list in the lib's Makefile.
> 
> Note raw.c has nothing todo with raw api, it's about raw (low-level)
> PCBs...
> 
> There is no 'API file' for this, you merely use
> all funcs in lwip/src/core directly instead of using the
> sequential API wrapper.

Ahh, thanks for clearing that up Christian, I was working from memory.
In that case, raw.c should by the sound of it definitely be in the list
of things the library compiles.  This should answer at least some of the
original question.  It also demonstrates that the Makefile needs fixing.
I'll see if I can find some time, but don't hold your breath!

Kieran