How to get the actual C code finally passed to compiler

[linq936]

Hi,
In the C code there are many #include and #define, I wonder if there
is a way I can see what is the final C file after all these pre-process
are done?

I am using Visual C compiler.

Thanks.

 

[Jim Langston]

Hi,
In the C code there are many #include and #define, I wonder if there
is a way I can see what is the final C file after all these pre-process
are done?

I am using Visual C compiler.

Thanks.

You should acutally ask in microsoft.public.vc but I think this will do it
for you:
project->properties->C/C++->Output Files->Expand Attributed Source [yes]

 

[red floyd]

Hi,
In the C code there are many #include and #define, I wonder if there
is a way I can see what is the final C file after all these pre-process
are done?

I am using Visual C compiler.

Thanks.

You should acutally ask in microsoft.public.vc but I think this will do it
for you:
project->properties->C/C++->Output Files->Expand Attributed Source [yes]

This is why you don't ask in this group. That's wrong. It's in
C/C++=>PreProcessor.

 

[Dietmar Kuehl]

In the C code there are many #include and #define, I wonder if there
is a way I can see what is the final C file after all these pre-process
are done?

All C and C++ compilers I have ever used supported the flag "-E"
which caused the compiler to spit out the preprocessed file. Of
course, I'm assuming you know how to compile your code from the
command line...