This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [gfortran] patch for mingw
- From: Mark Mitchell <mark at codesourcery dot com>
- To: François-Xavier Coudert<Francois-Xavier dot Coudert at ens dot fr>
- Cc: Danny Smith <dannysmith at users dot sourceforge dot net>, GCC Patches <gcc-patches at gcc dot gnu dot org>, fortran at gcc dot gnu dot org
- Date: Mon, 12 Sep 2005 10:39:14 -0700
- Subject: Re: [gfortran] patch for mingw
- References: <000701c5b5b2$1ded1510$716d65da@DANNY> <20050910080435.GA4164@clipper.ens.fr>
François-Xavier Coudert wrote:
> What do they refer to exactly? I guess __MINGW32__ is what i want, but is
> __WIN32 a strict equivalent? Or does it include cygwin systems? What
> about the difference between _WIN32 and __WIN32?
I don't remember what Cygwin defines exactly, any more. Things are a
bit confusing, because Cygwin does (or, at least, did?) define _WIN32,
as you say. I do not thing you should explicitly check __MINGW32__, as
it's really Cygwin that's the unique case. (For example, if you used
some other non-Cygwin Windows compiler, you'd want the same code as
__MINGW32__, unless it used some truly MinGW-specific code.)
So, I think:
defined(_WIN32) && !defined(__CYGWIN__)
really is what you want.
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304