Project properties -> C/C++ -> Preprocessing -> Preprocess to a file: Yes (/P)
The files will be called .i and will be created in the build directory.
Also see the msdn page.
More Related Contents:
- MSVC++ variadic macro expansion
- How to test if preprocessor symbol is #define’d but has no value?
- How do I temporarily disable a macro expansion in C/C++?
- Expand macro inside string literal
- C++ preprocessor __VA_ARGS__ number of arguments
- Will new return NULL in any case?
- Convert CString to const char*
- What does the operation c=a+++b mean?
- Why does VS not define the alternative tokens for logical operators?
- Is using #pragma warning push/pop the right way to temporarily alter warning level?
- Why do I need double layer of indirection for macros?
- Will C++ exceptions safely propagate through C code?
- Why aren’t static const floats allowed? [duplicate]
- Is std::string size() a O(1) operation?
- DLL References in Visual C++
- Exception Error c0000005 in VC++
- Is the backslash acceptable in C and C++ #include directives?
- “No newline at end of file” compiler warning
- C++20 constexpr vector and string not working
- Why does this program crash: passing of std::string between DLLs
- Double delete in initializer_list vs 2013
- How do YOU reduce compile time, and linking time for Visual C++ projects (native C++)?
- How does C++ Preprocessors work?
- LNK2038: mismatch detected for ‘RuntimeLibrary’: value ‘MT_StaticRelease’ doesn’t match value ‘MD_DynamicRelease’ in file.obj
- Visual Studio debugger error: Unable to start program Specified file cannot be found
- std::thread::join() hangs if called after main() exits when using VS2012 RC
- How can adding code to a loop make it faster?
- how to specify vc11 lambda calling convention
- C preprocessor macro specialisation based on an argument
- Access violation on static initialization