From:	ty AT kau1 DOT kodak DOT com (Trevor Yann)
Subject:	Re: Q: How to use WinSock and cygwin.dll together?
19 Dec 1996 15:34:32 -0800 :
Sender:	daemon AT cygnus DOT com
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<1.5.4.32.19961219231949.002f6130.cygnus.gnu-win32@mailhost>
Mime-Version:	1.0
X-Sender:	ty AT mailhost
X-Mailer:	Windows Eudora Light Version 1.5.4 (32)
Original-To:	"Geza Groma" <groma AT everx DOT szbk DOT u-szeged DOT hu>
Original-Cc:	gnu-win32 AT cygnus DOT com
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

At 01:41  19/12/1996 MET, you wrote:
>Understanding that cygwin32_getsockopt is not yet supported, I would 
>try to use the native WinSock functions instead of their cygwin32_ 
>counterparts to build Python. Well, I read the FAQ an followed the recent
discussion 
>on this topic, but it is still not clear, how can I do that.
>
>Could somebody explain what headers (sys/socket.h, 
>winsock.h, Windows32/Sockets.h or some modified version of these?),
>what definitions (__INSIDE_CYGWIN32__, __INSIDE_CYGWIN32_NET__?),
>and what library (-lwsock32?) should (not) I use?

Assuming that the source file will be only be using winsock functions
directly, you should #include winsock.h and use the functions directly, no
#defines required. It is important not to #include sys/socket.h, as it will
#define all of the function names.

It is more complicated if you have a source file that needs access to both
the winsock interface and the unix style socket interface at the same time.

>Thanks in advance,
>Geza Groma

-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -