Commit message says...

Allow compilation of libcurl and curl using BSD-style lwIP on Win32.

In order to compile libcurl and curl with this support it is necessary
to edit files lib/config-win32.h and src/config-win32.h and uncomment
a line to make definition of preprocessor symbol USE_LWIPSOCK.

Afterwards you can compile as usual.

In order to use compiled library with BSD-style lwIP TCP/IP stack in
your program it is mandatory that you include lwIP header file <lwip/opt.h>
before including <curl/curl.h> or <curl/multi.h>

Compilation has been verified with lwIP 1.4.0 and contrib-1.4.0 from:

http://download.savannah.gnu.org/releases/lwip/lwip-1.4.0.zip
http://download.savannah.gnu.org/releases/lwip/contrib-1.4.0.zip

Have fun!

Directly related with this are TODO issues # 294 and 301 which both
seem to arise from others attempt to use lwIP sockets on Win32 _BUT_
also using the winsock definitions from the configwin-32.h files. It
seems that unfortunately they didn't realize that the USE_WINSOCK
blocks are independent of the WIN32 blocks since long time ago. And
that if they wished to use a different stack other than the winsock
one they should have provided appropiate definitions for an
alternative stack instead of trying to hack at the USE_WINSOCK one.

I've made this happen, and have been able to compile curl and libcurl
with lwIP 1.4.0 sockets on Win32.

Support for configure capable builds will have to wait a bit longer.

It seems that lwIP TCP/IP stack with BSD-style interface is new in
lwIP 1.4.0, so test test test.

With this, I would directly close issue #294 pointing it to this mail.

-- 
-=[Yang]=-
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html