On Tue, Mar 3, 2009 at 6:17 PM, Geoff McLane <ubu...@geoffair.info> wrote: > > So while using the macro WIN32, meaning NOT unix, might be appropriate > for MINGW, but not _WIN32 unless the Mingw compiler also has this > predefine, it is also my understanding that this may mess with CYGWIN > building, but not sure on this... Maybe someone who uses and understands > the cygwin environment could comment on this.
mingw does define WIN32, _WIN32, __WIN32 and even __WIN32__ for good measure. I picked _WIN32 exactly because MSDN said that's the one predefined by MSVC as well and thus can be used to detect the platform without any headers included. Compiler-specific constructs (pragmas, attributes, etc) should still be conditional on _MSC_VER, of course. No idea about cygwin, but I guess these macros should only be defined when using the windows headers/dlls and not when using the cygwin layer. That would suit us fine, but we shall wait for a confirmation. -- Csaba/Jester ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
