CONFIG_* defines

[Allan Clark]

Vladimir N. Oleynik wrote:

> Bernhard,
>
>> regarding that 3). Can you please explain that a little bit?
>>
>>
>> We could just move the CONFIG_* namespace to something different,
>> for example BUSYBOX_APPLET_* and BUSYBOX_APPLET_*_{FOO,BAZ,...}
>> I know that the cons -- several patches in the bugtracker may not apply
>> cleanly any more etc. -- were already brought up..
>>
>> Just as an example, i'm attaching an applet runlevel(8). The only thing
>> which would need to be touched would be bbconfig for it to allow
>> BUSYBOX_* along the by then old/legacy CONFIG_* entries in .config.
>
>
> Why BUSYBOX_APPLET_NAME?
> I think, best is
> CONFIG_APPLETNAME, APPLET_FEATURE_NAME, BB_FEATURE_NAME. 

Busybox may co-exist with other projects that use Kconfig.  For example, 
I'd love to configure busybox at the root-level buildroot/.config, but 
that would mean it needs BUSYBOX_* symbols, or at least BB_*, then I 
would probably have to include the busybox Config.in files.  Hell, I'd 
like to see the kernel there too, or will that cause Kconfig to explode, 
showering spent bits and overflowed buffers all over my keyboard?

It's easy to see multiple CONFIG_INET, CONFIG_INETD, CONFIG_INSMOD, etc.

In short, I agree that BB_* or BUSYBOX_* is probably a good idea...

Allan