gcc option -E

Lin George george4academic@yahoo.com
Sat Oct 13 14:20:00 GMT 2007


Thanks Brian,


The links are very helpful! About your comments, could you let me know what do you mean *There's no way to know based only on what you've given.* please?

--------------------
As for why you'd want a file containing a list of all the #defines,
you'd have to look at the context of how it's used elsewhere in the
build system.  There's no way to know based only on what you've given.
--------------------


regards,
George

----- Original Message ----
From: Brian Dessent <brian@dessent.net>
To: Lin George <george4academic@yahoo.com>
Cc: gcc-help@gcc.gnu.org
Sent: Friday, October 12, 2007 11:07:15 PM
Subject: Re: gcc option -E

Lin George wrote:

> I have tried that in ListDef file (new generated after either of the two commands) and it contains several hundred lines of #define, typedef and some other definitions. Could anyone help to answer what is the function of the two commands? Differences between -dM and -dD?

The -E option enables preprocessing only.  Every option is documented in
the manual:

http://gcc.gnu.org/onlinedocs/gcc/Option-Index.html
http://gcc.gnu.org/onlinedocs/gcc/Preprocessor-Options.html

As for why you'd want a file containing a list of all the #defines,
you'd have to look at the context of how it's used elsewhere in the
build system.  There's no way to know based only on what you've given.

Brian


       
____________________________________________________________________________________
Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. 
http://answers.yahoo.com/dir/?link=list&sid=396545433



More information about the Gcc-help mailing list