From: noer@cygnus.com (Geoffrey Noer)
Subject: Re: Sockets in gnu-win32
2 Dec 1996 12:03:09 -0800
Sender: daemon@cygnus.com
Approved: cygnus.gnu-win32@cygnus.com
Distribution: cygnus
Message-ID: <199612020338.TAA03884.cygnus.gnu-win32@cirdan.cygnus.com>
Content-Type: text
Original-To: sos@prospect.com.ru (Sergey Okhapkin)
Original-Cc: noer@cygnus.com, gnu-win32@cygnus.com
In-Reply-To: <01BBDABF.B8A23EF0@bbs.prospect.com.ru> from "Sergey Okhapkin" at Nov 25, 96 10:59:19 am
X-Mailer: ELM [version 2.4 PL23]
Content-Length: 622       
Original-Sender: owner-gnu-win32@cygnus.com

> 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

The problem with this is that if we export the cygwin functions without the
cygwin32_ prefix in the dll, nobody can use WinSock while still using other
functions in the dll (they'd get multiple definition problems at link
time). As things stand, you can use the cygwin.dll and WinSock by
undefining the mapping from cygwin32_foo to foo in the header files.

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