From: earnie_boyd@yahoo.com (Earnie Boyd) Subject: Re: I: gcc ... -U_WIN32 ... may cause problems 29 Aug 1998 10:15:25 -0700 Message-ID: <19980829133256.3242.rocketmail.cygnus.gnu-win32@send103.yahoomail.com> Reply-To: earnie_boyd@yahoo.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: MCzapski@openplus.com.au, Michael Weiser Cc: gnu-win32@cygnus.com ---Michael Weiser wrote: > > Hello Michael, you wrote: > >Cygwin32 but unix-specific daemon code is compiled instead, for example. To > >avoid coding #if defined construct as shown I decided to undefine _WIN32 when > >compiling in Cygwin32 environment by using a command line of a form "gcc ... > >-U_WIN32 ...". Before I did that the application worked fine however as soon > Wouldn't it be cleaner and easier to code something like > > #if defined __unix__ || defined __CYGWIN32__ > ... > #endif > > and > > #if defined _WIN32 && !defined __CYGWIN32__ > ... > #endif > > around parts of your program that should behave like on unix under > cygwin? IMHO that wouldn't be more effort than solving your current > problem and all the others that will arise if something in the headers > or the cygwin tools gets changed. Since we are giving humble opinions here is mine: Leave the _WIN32 and WINNT for MS' use and get rid of them from the specs altogether. I've had to be cautious about this before and _WIN32 being defined for CYGWIN32 and even MINGW32 definitely gets in the way on occasion. _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".