Determining whether compiling on Windows or other system
Asked Answered
R

3

5

I'm currently developing a cross-platform C application. Is there any compiler macro which is defined only during compilation on Windows, so I can #ifdef some Windows specific #includes?

Typical example is selecting between WinSock and Berkeley sockets headers:

#ifdef _WINDOWS
   #include <winsock.h>    
#else
   #include <sys/socket.h>
   #include <netinet/in.h>
   #include <sys/un.h>
   #include <arpa/inet.h>
   #include <netdb.h>
#endif

So the thing I'm looking for is something like that _WINDOWS macro.

Randolphrandom answered 5/4, 2010 at 15:18 Comment(0)
M
11

Your best bet is to use

_WIN32

It is guaranteed to be defined when compiling for a 32-bit or 64-bit Windows platform using the Visual C++ compiler. I would expect other compilers for Windows to define it as well (the Intel C++ compiler defines it, as does the MinGW gcc).

Murry answered 5/4, 2010 at 15:19 Comment(2)
And what in case of 64-bit Windows? I presume _WIN32 is defined only on 32 bit systems, right?Randolphrandom
The 32 is really there to separate it from ancient 16-bit versions of Windows. Removing that definition in Win64 would've broken too much stuff, so it was less hassle to leave it in.Unipersonal
H
3

Use _WIN32.

Reference:

Harrisonharrod answered 5/4, 2010 at 15:24 Comment(0)
N
2
_WIN32  

Defined for applications for Win32 and Win64. Always defined.

_WIN64  

Defined for applications for Win64.

Source : Lists the predefined ANSI C and Microsoft C++ implementation macros.

Nottingham answered 5/4, 2010 at 15:23 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.