How do I generate an error or warning in the C preprocessor?

by

Place anywhere:

#ifndef DEBUG
#error "Only Debug builds are supported"
#endif

For reference: Diagnostics

More Related Contents:

  1. Pragma in define macro
  2. C Preprocessor, Stringify the result of a macro
  3. Can the C preprocessor perform integer arithmetic?
  4. Is the C99 preprocessor Turing complete?
  5. What exactly does an #if 0 ….. #endif block do?
  6. The role of #ifdef and #ifndef
  7. #define macro for debug printing in C?
  8. Why are preprocessor macros evil and what are the alternatives?
  9. #pragma pack effect
  10. How do I see a C/C++ source file after preprocessing in Visual Studio?
  11. Real-world use of X-Macros
  12. Easy way to use variables of enum types as string in C?
  13. How do I check OS with a preprocessor directive?
  14. How to detect reliably Mac OS X, iOS, Linux, Windows in C preprocessor? [duplicate]
  15. Stringification of a macro value
  16. What is the meaning of lines starting with a hash sign and number like ‘# 1 “a.c”‘ in the gcc preprocessor output?
  17. Combining C++ and C – how does #ifdef __cplusplus work?
  18. How to compare strings in C conditional preprocessor-directives
  19. Define preprocessor macro through CMake?
  20. What does ## mean for the C(C++) preprocessor?
  21. Representing big numbers in source code for readability?
  22. Can macros be overloaded by number of arguments?
  23. When can you omit the file extension in an #include directive?
  24. C preprocessor: expand macro in a #warning
  25. Concat two `const char` string literals
  26. What is a good reference documenting patterns of use of X-Macros in C (or possibly C++)?
  27. What is the NDEBUG preprocessor macro used for (on different platforms)?
  28. Is there a way to do a #define inside of another #define?
  29. offsetof at compile time
  30. Using Parentheses in Define Preprocessor Statements

Leave a Comment