From:	sos AT prospect DOT com DOT ru (Sergey Okhapkin)
Subject:	RE: Sockets in gnu-win32
25 Nov 1996 01:26:43 -0800 :
Sender:	daemon AT cygnus DOT com
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<01BBDABF.B8A23EF0.cygnus.gnu-win32@bbs.prospect.com.ru>
Original-To:	"'Geoffrey Noer'" <noer AT cygnus DOT com>
Original-Cc:	"gnu-win32 AT cygnus DOT com" <gnu-win32 AT cygnus DOT com>
Encoding:	13 TEXT
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

Geoffrey Noer wrote:

>In normal use, you will get the cygwin32 sockets.  However, if you choose
>to use WinSock, you can do so without giving up access to the rest of the
>Cygwin32 API simply by not including the <sys/socket.h> header.
>
>If anyone can think of a better way of doing this, please let me know...

As for me, the best solution is to export cygwin functions with normal 
names (without cygwin32_ prefix). If one choose to use WinSock, he will 
have to add -lwsock32 to gcc command line.
Sergey Okhapkin
Moscow, Russia

-
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 -