Gisle Vanem wrote:
> Mason wrote:
>
>> My main difficulty is the close function, because it is
>> defined both in libc.a, to deal with regular files, and
>> in lip.a, to deal with sockets.
>>
>> I suppose the simple solution would be to convince libcurl
>> to use lwip_close instead of close?
>
>
"Mason" wrote:
My main difficulty is the close function, because it is
defined both in libc.a, to deal with regular files, and
in lip.a, to deal with sockets.
I suppose the simple solution would be to convince libcurl
to use lip_close instead of close?
Didn't the thread on the libcurl-list w
On Tue, 2012-03-13 at 17:16 +0100, Mason wrote:
> The preload trick works on dynamic-link systems, right?
>
> (Everything is statically linked on my system.)
Yes, if you're statically linked you'll have to modify libcurl or libc
to call lwIP when appropriate.
Kieran
__
Kieran Mansley wrote:
> If you could arrange for lwIP to use a different range of socket IDs
> from the file descriptors used by libc then you could easily make a
> wrapper function that would call the appropriate function (libc close or
> lwip_close) based on the fd provided. This would then all
On Tue, 2012-03-13 at 16:40 +0100, Mason wrote:
>
> I'd be happy to hear suggestions, opinions, comments...
If you could arrange for lwIP to use a different range of socket IDs
from the file descriptors used by libc then you could easily make a
wrapper function that would call the appropriate fu
Hello,
I'm trying to port libcurl on top of lwip.
http://en.wikipedia.org/wiki/CURL
http://en.wikipedia.org/wiki/LwIP
My main difficulty is the close function, because it is
defined both in libc.a, to deal with regular files, and
in lwip.a, to deal with sockets.
I suppose the simple solution wo
