This is the mail archive of the
mailing list for the Cygwin project.
Re: I: gcc ... -U_WIN32 ... may cause problems
- To: MCzapski at openplus dot com dot au, Michael Weiser <michael at weiser dot saale-net dot de>
- Subject: Re: I: gcc ... -U_WIN32 ... may cause problems
- From: Earnie Boyd <earnie_boyd at yahoo dot com>
- Date: Sat, 29 Aug 1998 06:32:56 -0700 (PDT)
- Cc: gnu-win32 at cygnus dot com
- Reply-To: earnie_boyd at yahoo dot com
---Michael Weiser <firstname.lastname@example.org> wrote:
> Hello Michael, you wrote:
> >Cygwin32 but unix-specific daemon code is compiled instead, for
> >avoid coding #if defined construct as shown I decided to undefine
> >compiling in Cygwin32 environment by using a command line of a form
> >-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__
> #if defined _WIN32 && !defined __CYGWIN32__
> 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
"email@example.com" with one line of text: "help".