Re: Kconfig troubles when using menuconfig - Was: [patch]Re:[linux-usb-devel] linux-2.6.22-rc5-gf1518a0 build #300 failed in zc0301_core.c

[Roman Zippel]

Hi,

On Sat, 23 Jun 2007, Jan Engelhardt wrote:

> Would it make sense to define a new entity called "configmenu" (or something
> else) that is equivalent to menuconfig with the following changes?
> 
>  * it creates a CM_ variable instead of a CONFIG_ one
>  * the CM_ symbols are not available to Makefiles or C files
>    (so in fact, just to menuconfig and that they are listed in .config)

I really don't understand why this should be needed in first place.
Where is the problem with using tristate? Nobody forces anyone to set it 
to 'm' if you don't like it. I could also argue it easily allows me to 
quickly restrict enclosed options to module status. It's just another 
choice, where is that fascination coming from that it has to be an on/off 
switch?
Whether the config option is visible in the Makefile and produces any 
code, is completely irrelevant in this context, as the user trying to 
configure the kernel has no idea of it.

bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/