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 X-Apparently-From: Message-ID: <3A805F11.A86C8A8E@yahoo.com> Date: Tue, 06 Feb 2001 15:31:13 -0500 From: Earnie Boyd Reply-To: Earnie Boyd X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: cygwin-developers AT cygwin DOT com Subject: Re: [Fwd: [MinGW-dvlpr] winsock2.h] References: <3A7F737F DOT 31746D8E AT yahoo DOT com> <20010205233217 DOT A4786 AT redhat DOT com> <20010206211152 DOT E15821 AT cygbert DOT vinschen DOT de> <20010206151724 DOT E9005 AT redhat DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Christopher Faylor wrote: > > 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? > The more I study this the more I think we can remove the whole !(...) test anyway. If you don't want the winsock.h header just undef Win32_Winsock if you want it undef WIN32_LEAN_AND_MEAN and define Win32_Winsock. Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com