This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: #ifdef tool?

To: dorin at gr-303 dot com
Subject: Re: #ifdef tool?
From: "William A. Gatliff" <bgat at saturn dot billgatliff dot com>
Date: Tue, 24 Jul 2001 20:07:47 -0500
Cc: crossgcc at sources dot redhat dot com
References: <200107242213.RAA98519@puma.chaski.com>
Reply-To: bgat at billgatliff dot com

Mike:

Maybe gcc's -E option is what you want.

b.g.

On Tue, Jul 24, 2001 at 05:13:24PM -0500, Michael Dorin wrote:
> 
> 
> Anybody know of a tool that could strip unused ifdefs right from your code?
> 
> Something that could look at your include path and your -D's and generate
> a source file, with comments, with all the undefined code removed?
> 
> Could you do this with the cpp?
> 
> If have a collection of code with lots of #ifdefs.  I would really like
> to be able easily see what I am compiling.  
> 
> Thanks for any advice.
> 
> -Mike 
> 
> 
> 
> ------
> Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
> Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
> 

-- 
Bill Gatliff
bgat@billgatliff.com

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com

References:
- #ifdef tool?
  - From: Michael Dorin

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]