Re: [PATCH] headerdep: a tool for detecting inclusion cycles in header file

[Julia Lawall <julia@diku.dk>]

On Sat, 26 Apr 2008, Adrian Bunk wrote:

> On Sat, Apr 26, 2008 at 03:45:54PM +0200, Vegard Nossum wrote:
> > Hi Sam,
> > 
> > Maybe something like this could be useful for cleaning up headers (and
> > maintaining that cleanliness once it has been achieved). What do you think?
> > 
> > (One thing which might or might not be good is that 'make headerdep' will
> >  also compile using CC if they're not already compiled. If this should be
> >  fixed, I think you'd know how to do it.)
> 
> This way you only catch problems in the current kernel configuration.
> 
> The only problems are under include/, and you should be able to do this 
> by parsing all headers and without hooking into the build system.

I guess one would still have to consider all of the possible permutations 
of values of configuration variables, to interpret the #ifdefs that have 
an impact on what is included?  A quick grep suggests that they are mostly 
related to  __KERNEL__, so perhaps it would not be too expensive to do.

julia