[BusyBox] CONFIG_ name clashing with kernel
Rob Landley
rob at landley.net
Tue Aug 2 06:17:55 UTC 2005
On Monday 01 August 2005 17:42, Shaun Jackman wrote:
> On 8/1/05, Rob Landley <rob at landley.net> wrote:
> >> we can rename these three defines (SYSCTL/TR/WATCHDOG) or we could take
> >> care of this now (and forever) by replacing all of the macros with a
> >> different namespace:
> >
> > BB_CONFIG_*> Let's not make the prefix longer, thanks.
>
> I agree entirely. I like the BB_ prefix though. How about
> BB_FEATURE_xxx instead? (i.e. s/CONFIG_/BB_/)
BB_ isn't bad, and it's vaguely greppable. And we've got FEATURE_ all over
the place already (CONFIG_FEATURE became ENABLE_FEATURE_...)
However: the fundamental question is: for 1.1 do we want to rip out all the
CONFIG_ symbols, have bb_config.h stop including #config.h, and do a
transition over fixing up all the #ifdefs that break to use the new 1 or 0
symbols instead of #ifdef/#undef?
If you're worried about namespace pollution, we're going to have to have a big
cleanup patch at some point...
Rob
More information about the busybox
mailing list