Mark Levedahl <mleved...@gmail.com> writes:
> Cygwin and Windows should be treated as completely separate platforms:
> if __CYGWIN__ is defined, do one thing, if not, go ahead and check
> WIN32, but the WIN32 macro should never be tested once we know the
> platform is CYGWIN - these really are different platforms (if you are
> unsure of this, consider that Cygwin includes a cross-compiler to
> target native Win32 as the Cygwin maintainers recognized the platforms
> are different).
Not disagreeing with your conclusion (they should be treated as
different), why does it define WIN32 in the first place?
Perhaps we would want
#ifdef __CYGWIN__
#undef WIN32
#endif
very early in some include file before nothing else is included?
Just being curious.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
