Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com Date: Wed, 27 Sep 2000 09:57:54 -0400 Message-Id: <200009271357.JAA12367@envy.delorie.com> From: DJ Delorie To: egb@us.ibm.com CC: cygwin@sourceware.cygnus.com In-reply-to: (egb@us.ibm.com) Subject: Re: Linking in WSAGetLastError References: > 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@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@sourceware.cygnus.com