Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Tue, 6 Feb 2001 15:17:24 -0500 From: Christopher Faylor To: cygwin-developers Subject: Re: [Fwd: [MinGW-dvlpr] winsock2.h] Message-ID: <20010206151724.E9005@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers References: <3A7F737F DOT 31746D8E AT yahoo DOT com> <20010205233217 DOT A4786 AT redhat DOT com> <20010206211152 DOT E15821 AT cygbert DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <20010206211152.E15821@cygbert.vinschen.de>; from vinschen@redhat.com on Tue, Feb 06, 2001 at 09:11:52PM +0100 On Tue, Feb 06, 2001 at 09:11:52PM +0100, Corinna Vinschen wrote: >On Mon, Feb 05, 2001 at 11:32:17PM -0500, Christopher Faylor wrote: >> On Mon, Feb 05, 2001 at 10:46:07PM -0500, Earnie Boyd wrote: >> >Danny Smith wrote: >> > >> >> This is what's in windows.h now. >> >> >> >> #ifndef WIN32_LEAN_AND_MEAN >> >> #include >> >> #include >> >> #include >> >> #include >> >> #include >> >> #include >> >> #include >> >> #include >> >> #include >> >> #include >> >> #include >> >> #include >> >> #if defined(Win32_Winsock) || >> >> !(defined(__INSIDE_CYGWIN__) || defined(__CYGWIN__) || defined >> >> (__CYGWIN32__) || defined(_UWIN)) >> >> #include >> >> #endif >> >> #endif /* WIN32_LEAN_AND_MEAN */ >> > >> >Is this __INSIDE_CYGWIN__ needed? Danny's trying to clean up the winsock.h and >> >winsock2.h header files. >> >> Dunno. Should be pretty simple to find out. Try building Cygwin with it >> removed. > >AFAIK, it's needed. If you build an application using native windows >calls you need to include windows.h. But you _never_ should include >winsock.h when linking against cygwin1.dll since the socket calls >colide then. Except inside of Cygwin which obviously needs winsock.h. > >So the problem here is not building cygwin itself but to build a cygwin >application using both, native windows calls and cygwin socket calls. I don't understand the logic, though. When is __INSIDE_CYGWIN__ defined when __CYGWIN__ is not defined? cgf