[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070929202444.GA20884@uranus.ravnborg.org>
Date: Sat, 29 Sep 2007 22:24:44 +0200
From: Sam Ravnborg <sam@...nborg.org>
To: Ingo Oeser <ioe-lkml@...eria.de>
Cc: Randy Dunlap <randy.dunlap@...cle.com>,
Erez Zadok <ezk@...sunysb.edu>, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
"Kok, Auke" <auke-jan.h.kok@...el.com>,
Kyle Moffett <mrmacman_g4@....com>,
Jan Engelhardt <jengelh@...putergmbh.de>,
Adrian Bunk <bunk@...nel.org>, roel <12o3l@...cali.nl>
Subject: Re: [OT] kbuild syntax extension for ccflags and asflags (was: [PATCH 1/3] CodingStyle updates)
> > Lately I have considered extending the kbuild syntax a bit.
> >
> > Introducing
> > ccflags-y
> > asflags-y
> >
> > [with same functionality as the EXTRA_CFLAGS, EXTRA_AFLAGS]
> > would allow us to do:
> >
> > ccflags-$(CONFIG_WHATEVER_DEBUG) := -DDEBUG
>
> Please do!
>
> That is very useful for testing and developing new modules.
> I learnt a lot from you in this regard and used that kind
> of syntax to the extreme in some other non-kernel project
> of mine. There it included also ccflags, asflags and so on.
>
> I further split that into -debug-y and -optimize-y flags,
> but that was just for my own convenience.
Thanks for feedback Ingo.
I just started a new thread were I outlined the ideas I have
for further extending (some may say uglifying) the kbuild syntax.
I will see the outcome of this thread before implmenting something.
PS. The implementation part is obviously trivial, the
hard part is the documentation :-)
Sam
-
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