[ECOS] strip gcc preprocessor directives?

[ECOS] strip gcc preprocessor directives?

[A Roturier]

hello,

i'd like to strip off those gcc preprocessor directives so the source codes 
are
more readable.

i browsed through gcc online help and found the argument,

arm-elf-gcc -Wa,-a=out.txt .........

but in out.txt file those directives were still there(#ifdef, #else.. etc).
is there any way to accomplish this?

thanx for help,
kc

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

Re: [ECOS] strip gcc preprocessor directives?

[Daniel Morris]

On Mon, Jul 23, 2001 at 01:17:39PM +0000, A Roturier wrote:
> hello,
> 
> i'd like to strip off those gcc preprocessor directives so the source codes 
> are
> more readable.
> 
> i browsed through gcc online help and found the argument,
> 
> arm-elf-gcc -Wa,-a=out.txt .........

Either invoke the C preprocessor directly, or feed arm-elf-gcc the
-E flag. Note you'll need to pass your usual definitions and macros,
or else the source you'll be reading won't match what is going to
be compiled!

 Daniel

Re: [ECOS] strip gcc preprocessor directives?

[I-Jui Sung]

There exists some useful UNIX tools for removing conditional compilation
preprocessor directives (but not
expanding macros, substituting #defines to their values, etc. )

try to gogle `scpp' or `unifdef'.

Regards,
IJS
----- Original Message -----
From: "Daniel Morris" <danielm@redhat.com>
To: "A Roturier" <roturier@hotmail.com>
Cc: <ecos-discuss@sources.redhat.com>
Sent: Monday, July 23, 2001 11:58 PM
Subject: Re: [ECOS] strip gcc preprocessor directives?


> On Mon, Jul 23, 2001 at 01:17:39PM +0000, A Roturier wrote:
> > hello,
> >
> > i'd like to strip off those gcc preprocessor directives so the source
codes
> > are
> > more readable.
> >
> > i browsed through gcc online help and found the argument,
> >
> > arm-elf-gcc -Wa,-a=out.txt .........
>
> Either invoke the C preprocessor directly, or feed arm-elf-gcc the
> -E flag. Note you'll need to pass your usual definitions and macros,
> or else the source you'll be reading won't match what is going to
> be compiled!
>
>  Daniel