DDK preprocessor directives
Does the DDK's build environments pass preprocessor defines to code to specify x86/ia64/x64 for the code to use with #ifdef, etc.?
From what I've seen it does not. However, when setting up your makefile, make i385, amd64 and ia64 directories and store your separate code files in those. Then, in your sources file, use the I386_SOURCES=, AMD64_SOURCES= and IA64_SOURCES= vars, respectively, to specify the source files. This works with .asm files, and should work with all other .c files as well.
Yes. Look at Predefined Macros Also you can see a lot of such statements in DDK include files: #if defined(_M_MRX000) || defined(_M_ALPHA) || defined(_M_PPC) || defined(_M_IA64) || defined(_M_AMD64) #define UNALIGNED __unaligned #if defined(_WIN64) #define UNALIGNED64 __unaligned #else #define UNALIGNED64 #endif #else #define UNALIGNED #define UNALIGNED64 #endif
I want to nest include files inside include files. Why cant I do that in Inno Setup?
Discriminating between (small) numbers and everything else in C preprocessor
Defining preprocessor symbols for CLion analyzer
Check multiple conditions at once using m4 preprocessor
XC8 warning: (107) illegal # directive “foo”
Compiling with ocamlbuild and camlp5
How not to output comments using the -C operation in mcpp
C++ Builder File Version not correct
How do you a preprocess statement for #include
Does the preprocessor pass environment variables?
YAML preprocessor / macro processor
Pre-Processing using m4
Is there a practical reason for “#if defined(X) && (X != 0)”?
How to check for presence of a directory in Inno Setup preprocessor?
What are analogs of “#ifdef”, “#ifndef”, “#else”, “#elif”, “#define”, “#undef” in D programming lnaguage?
Image pre-processing in OCR