Are there any macros to determine if my code is being compiled to Windows? [duplicate]

by

[Edit: I assume you want to use compile-time macros to determine which environment you’re on. Maybe you want to determine if you’re running on Wine under Linux or something instead of Windows, but in general, your compiler targets a specific environment, and that is either Windows (DOS) or it isn’t, but it’s rarely (never?) both.]

Some compilers offer macros to indicate a Windows build environment. But these will vary from compiler to compiler, and even on the same compiler on Windows if the target environment is not exclusively windows. Usually it’s __WIN32__, but not always.

#if defined (__WIN32__)
  // Windows stuff
#endif

Sometimes it can be _WIN32, __CYGWIN32__, or possibly just the compiler indicator (_MSC_VER).

If you know the environment you’ll be building in (from the makefile) then you can usually pass in the #define on the command line, like “g++ -D __WIN32__ yourfile.c“.

A little more info here

More Related Contents:

  1. What is the difference between #include and #include “filename”?
  2. Why use apparently meaningless do-while and if-else statements in macros?
  3. C/C++ maximum stack size of program on mainstream OSes
  4. C++ preprocessor __VA_ARGS__ number of arguments
  5. C/C++ macro string concatenation
  6. Can we have recursive macros?
  7. When are C++ macros beneficial? [closed]
  8. C/C++ line number
  9. Error: invalid operands of types ‘const char [35]’ and ‘const char [2]’ to binary ‘operator+’
  10. How to identify platform/compiler from preprocessor macros?
  11. Common array length macro for C? [duplicate]
  12. Can you make custom operators in C++?
  13. C/C++, can you #include a file into a string literal? [duplicate]
  14. Portability of #warning preprocessor directive
  15. How to make G++ preprocessor output a newline in a macro?
  16. C/C++ macro/template blackmagic to generate unique name
  17. Difference between Enum and Define Statements
  18. macro definition containing #include directive
  19. What does “#define STR(a) #a” do?
  20. C++: Can a macro expand “abc” into ‘a’, ‘b’, ‘c’?
  21. GCC, stringification, and inline GLSL?
  22. “No newline at end of file” compiler warning
  23. Header file included only once in entire program?
  24. Confused by squaring macro SQR in c [duplicate]
  25. What is the difference between #define and const? [duplicate]
  26. C++ #include semantics
  27. Is there a way to do a #define inside of another #define?
  28. How can I see the output of the Visual C++ preprocessor? [duplicate]
  29. Are Variadic macros nonstandard?
  30. #ifdef vs #if – which is better/safer as a method for enabling/disabling compilation of particular sections of code?

Leave a Comment