delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1997/06/06/21:09:18

From: sos AT prospect DOT com DOT ru (Sergey Okhapkin)
Subject: RE: libwinsock.a? Using mu own socket routines ...?
6 Jun 1997 21:09:18 -0700 :
Approved: cygnus DOT gnu-win32 AT cygnus DOT com
Distribution: cygnus
Message-ID: <01BC7263.6F9DC2B0.cygnus.gnu-win32@gater.krystalbank.msk.ru>
Original-To: "'gnu-win32 AT cygnus DOT com'" <gnu-win32 AT cygnus DOT com>,
"'Michael Anderson'"
<mka AT redes DOT int DOT com DOT mx>
Encoding: 18 TEXT
Original-Sender: owner-gnu-win32 AT cygnus DOT com

Michael Anderson wrote:
> I have done my own socket mappings and wish to use them instead of the
> provided cygwin32_socket() family of routines in sys/socket.h and
> netdb.h. When I comment-out the mapping defines in these two files, the
> compiler complains that socket(), accept(), etc are unresolved
> references. My code has correct prototypes. If I add -lwsock32 to the
> compile line, only WSAStartup() and WSACleanup are resolved.

#define Win32_Winsock          
#include <windows.h>

Of course, you must add -lwsock32 to compiler's command line. I just compiled with gcc and ran native winsock code.

-- 
Sergey Okhapkin
Moscow, Russia
Looking for a job.


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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019