Re: predefined preprocessor macros on Windows platforms

2007-02-15 Thread Simon Josefsson
Bruno Haible <[EMAIL PROTECTED]> writes: > Brian Dessent wrote: >> This should be __CYGWIN__ and not __CYGWIN32__. > > Yes, you are right. My bad. Here is the corrected summary: This is very useful, and I have been referencing to your posts describing this a few times. Would it be possible to pu

Re: predefined preprocessor macros on Windows platforms

2007-02-15 Thread Bruno Haible
Brian Dessent wrote: > This should be __CYGWIN__ and not __CYGWIN32__. Yes, you are right. My bad. Here is the corrected summary: 1) The compiler indicators: - Mingw, Cygwin: __GNUC__ - MSVC: _MSC_VER - Borland:__TURBOC__, __BORLANDC__ 2) The CPU indicators for x86: -

Re: predefined preprocessor macros on Windows platforms

2007-02-15 Thread Brian Dessent
Bruno Haible wrote: > 3) Operating system: > - Cygwin default: __CYGWIN32__ > - Cygwin when the installer wants to use native Woe32 API (option -mwin32): > __CYGWIN32__, _WIN32 This should be __CYGWIN__ and not __CYGWIN32__. The former is the canonical name, the latter is

predefined preprocessor macros on Windows platforms

2007-02-15 Thread Bruno Haible
Hi, This is the yearly FAQ posting about the symbols defined on C/C++ compilations on Windows. 1) The compiler indicators: - Mingw, Cygwin: __GNUC__ - MSVC: _MSC_VER - Borland:__TURBOC__, __BORLANDC__ 2) The CPU indicators for x86: - Mingw, Cygwin: _X86_, __i386__ -