Re: [Mingw-users] Re: Make configuration for Win32.

[Luke D. <cod...@ho...>]

I don't quite understand what is wrong with _WIN32, but I also wouldn't
object to __WINDOWS32__, etc. (but I agree with Danny that WINDOWS32 is no
good for a compiler built-in). Since only Mingw (and Cygwin I guess) will
define __WINDOWS32__ (AFAIK), checking for this macro will really just be
checking for Mingw, but if that's what you want to do then __MINGW32__ would
be a better option. Then again, you probably need special build processes
for MSVC and other Windows compilers anyway, so explicitly defining
__WINDOWS32__ for those wouldn't be a problem.

Luke Dunstan

----- Original Message -----
From: "Earnie Boyd" <ear...@ya...>
To: "Paul D. Smith" <ps...@gn...>
Cc: <min...@li...>; <mak...@gn...>
Sent: Tuesday, September 10, 2002 9:51 AM
Subject: Re: [Mingw-users] Re: Make configuration for Win32.


> "Paul D. Smith" wrote:
> >
> > %% Earnie Boyd <ear...@ya...> writes:
> >
> >   eb> Ok then, how about __WINDOWS32__ or __WINDOWS32 and we'll
> >   eb> predefine it.
> >
> > If you prefer, but why not just leave it as-is?
> >
>
> I'm offering to add it to the list predefined macros.  Since this is
> implementation specific we should identify it as such.  Since you don't
> have an objection to either we'll choose one and submit a patch.
>
> Thanks,
> Earnie.