This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: I: gcc ... -U_WIN32 ... may cause problems
- To: earnie_boyd at yahoo dot com
- Subject: Re: I: gcc ... -U_WIN32 ... may cause problems
- From: Geoffrey Noer <noer at cygnus dot com>
- Date: Thu, 10 Sep 1998 18:54:18 -0700
- Cc: Mumit Khan <khan at xraylith dot wisc dot edu>, gw32 <gnu-win32 at cygnus dot com>
- References: <19980910155429.26532.rocketmail@send104.yahoomail.com>
On Thu, Sep 10, 1998 at 08:54:29AM -0700, Earnie Boyd wrote:
[...]
> Geoffrey, __CYGWIN32__ means "access to both Win32 API calls and
> Unix/Posix API calls". _WIN32 means "access to only Win32 API calls".
> __MINGW32__ means "access to only Win32 API calls" (Actually could be
> dropped in favor of _WIN32).
Although I understand why people might argue for your definitions,
this is *not* how we've been using them in any of the tools shipped as
part of the gnu-win32 releases.
We've always used __CYGWIN32__ to conditionalize code inclusion on
access to the Cygwin32 API (checking for the existance of Unixy
calls). We've used _WIN32 to check for accessibility of the Win32 API
calls. And finally, we've used _MSC_VER to identify code that's only
intended for VC++.
--
Geoffrey Noer
noer@cygnus.com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".