Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Wed, 27 Sep 2000 09:57:54 -0400
Message-Id: <200009271357.JAA12367@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: egb AT us DOT ibm DOT com
CC: cygwin AT sourceware DOT cygnus DOT com
In-reply-to: <OF0218AED7.F7BEE650-ON85256967.0048A37B@raleigh.ibm.com>
	(egb AT us DOT ibm DOT com)
Subject: Re: Linking in WSAGetLastError
References:  <OF0218AED7 DOT F7BEE650-ON85256967 DOT 0048A37B AT raleigh DOT ibm DOT com>


> I'm missing something here. If the CYGWIN libraries don't export
> functions (aren't current with MS API's) then you simply can't use
> the function.

I don't see the connection with proper prototyping, but anyway...

gcc under cygwin links in a handful of libraries *every time*,
including the standard user32, gdi32, and kernel32 libraries (where
MessageBox AT 16 is exported, for example).  Just because cygwin itself
doesn't export the win32 functions doesn't mean you can't get them
from windows itself.  Cygwin includes import libraries for 65 system
DLLs total.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com