Hello,
Is it possible to configure lwip in such a way that the static
library I build exports the /real/ BSD socket API function names?
I.e. export foo instead of lwip_foo (for socket, connect, bind, etc)
I'm trying to port libcurl on top of lwip, and it expects an actual
BSD socket implementatio
Mason wrote:
> Is it possible to configure lwip in such a way that the static
> library I build exports the /real/ BSD socket API function names?
> I.e. export foo instead of lwip_foo (for socket, connect, bind, etc)
I don't think it's currently possible without modifying the sources. I'd
sugges
Simon Goldschmidt wrote:
> Mason wrote:
>
>> Is it possible to configure lwip in such a way that the static
>> library I build exports the /real/ BSD socket API function names?
>> I.e. export foo instead of lwip_foo (for socket, connect, bind, etc)
>
> I don't think it's currently possible withou
Mason wrote:
> However, this was a red herring, and I'm still stuck building
> libcurl. I think the main problem is that the lwip header
> naming might not be 100% POSIX compliant, and libcurl can't
> find a lot of network related declarations.
>
> I think I saw some discussion or bug reports con
Simon Goldschmidt wrote:
> Mason wrote:
>
>> However, this was a red herring, and I'm still stuck building
>> libcurl. I think the main problem is that the lwip header
>> naming might not be 100% POSIX compliant, and libcurl can't
>> find a lot of network related declarations.
>>
>> I think I saw
