[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0804261720060.2756@ask.diku.dk>
Date: Sat, 26 Apr 2008 17:21:52 +0200 (CEST)
From: Julia Lawall <julia@...u.dk>
To: Adrian Bunk <bunk@...nel.org>
Cc: Vegard Nossum <vegard.nossum@...il.com>,
Sam Ravnborg <sam@...nborg.org>,
Pekka Enberg <penberg@...helsinki.fi>,
linux-kbuild@...r.kernel.org, kernel-janitors@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] headerdep: a tool for detecting inclusion cycles in
header file
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists