Comments on: How to get the preprocessed C / C++ source files? http://weseetips.com/2008/06/12/how-to-get-the-preprocessed-c-cpp-source-files/ Gold mine of Visual C++ tricks! Thu, 12 Jan 2012 15:10:53 +0000 hourly 1 http://wordpress.org/?v= By: Professor Rodolfo Martinez http://weseetips.com/2008/06/12/how-to-get-the-preprocessed-c-cpp-source-files/comment-page-1/#comment-154 Professor Rodolfo Martinez Fri, 19 Jun 2009 23:37:24 +0000 http://weseetips.wordpress.com/?p=167#comment-154 It would be highly desirable for the IDE to generate the preprocessed output in a specified (fixed name) file and then continue with the compiling and linking process without resulting later in link errors as reported here. By default, the file would contain the preprocessed output of the last file compiled. With this approach, resources available for debugging a program would include this valuable preprocessed information without the need to set up switches or other complications such as linking errors downstream. It would be highly desirable for the IDE to generate the preprocessed output in a specified (fixed name) file and then continue with the compiling and linking process without resulting later in link errors as reported here. By default, the file would contain the preprocessed output of the last file compiled. With this approach, resources available for debugging a program would include this valuable preprocessed information without the need to set up switches or other complications such as linking errors downstream.

]]> By: s http://weseetips.com/2008/06/12/how-to-get-the-preprocessed-c-cpp-source-files/comment-page-1/#comment-153 s Wed, 25 Jun 2008 06:59:06 +0000 http://weseetips.wordpress.com/?p=167#comment-153 So this flag is used only for checking the preprocessed output of an input file. So this flag is used only for checking the preprocessed output of an input file.

]]> By: s http://weseetips.com/2008/06/12/how-to-get-the-preprocessed-c-cpp-source-files/comment-page-1/#comment-152 s Wed, 25 Jun 2008 06:58:41 +0000 http://weseetips.wordpress.com/?p=167#comment-152 During this process actual object file generation is not done. Thats why the link error. This /P flag can be used evenif some compilation errors are present in the source file :) So this flag is only checking the preprocessed output of an input file. During this process actual object file generation is not done. Thats why the link error. This /P flag can be used evenif some compilation errors are present in the source file :)

So this flag is only checking the preprocessed output of an input file.

]]> By: Jijo.Raj http://weseetips.com/2008/06/12/how-to-get-the-preprocessed-c-cpp-source-files/comment-page-1/#comment-151 Jijo.Raj Tue, 17 Jun 2008 04:33:39 +0000 http://weseetips.wordpress.com/?p=167#comment-151 Nishad, You are right. Me too had the same link error. But the intermediate files are generated. Happy to know that the /P serve your need. ;) Nishad, You are right. Me too had the same link error. But the intermediate files are generated. Happy to know that the /P serve your need. ;)

]]> By: Nishad S http://weseetips.com/2008/06/12/how-to-get-the-preprocessed-c-cpp-source-files/comment-page-1/#comment-150 Nishad S Mon, 16 Jun 2008 04:50:55 +0000 http://weseetips.wordpress.com/?p=167#comment-150 Really nice and useful tip. But got link error when I used that. I created a dlg based app. And given the /P option and built the source. Then I got a link error LINK : fatal error LNK1104: cannot open file ".\Debug\PreProcExp.obj" If I remove the /P option then I will get the build successfully. Anyway I could see the intermediate macro expanded files... :) Really nice and useful tip.

But got link error when I used that. I created a dlg based app. And given the /P option and built the source. Then I got a link error LINK : fatal error LNK1104: cannot open file “.\Debug\PreProcExp.obj”

If I remove the /P option then I will get the build successfully.

Anyway I could see the intermediate macro expanded files… :)

]]>