[RFC][PATCH] kconfig: implement select with values
sam at ravnborg.org
Tue Jul 27 16:45:23 EST 2010
> Cute. I didn't know this was possible. I'll give it a try and see
> how it works for me. Do override config options also pickup
> select/depends constraints applied by later definitions? I think that
> would be necessary to kick out warnings when a defconfig selection
> isn't actually achievable.
kconfig allows one to add more properties to a config
symbol by defining the symbol again.
prompt "foo prompt"
Is the same as:
prompt "foo prompt"
The abvoe four lines can be located in different files.
And likewise kconfig allows the same property to be
specified twice or more.
So it is OK to say:
tristate "bar prompt"
Here kconfig just picks the first default is see.
And the example in my original mail uses the feature
that we can specify several defaults - and kconfig uses the first.
For choices the same is possible but then you need to use
a named choice - something that no one does today in the kernel.
Here we change the default to M386 which becomes the
selected if we use "alldefconfig".
[Note: It does not work until we use named choices in arch/x86/Kconfig.cpu]
> > Now in the original suggestion of Linus he used:
> > KBUILD_KCONFIG=Mykconfig make allnoconfig
> > And "allnoconfig" would make the modified defaults useless.
> > But the soon-to-be-introduced alldefconfig is more sensible.
> > alldefconfig uses default values for everything.
> I basically used defconfig in the prototype that I posted. I think it
> works well for me, and I've got it integrated into the build targets
> (just like Stephen's earlier patch) without having to do a
> KBUILD_KCONFIG trick.
"defconfig" with an empty file gives same config as "alldefconfig" so
it makes sense. But we wanted to drop the use of defconfig files
in favour of files with Kconfig syntax.
So alldefconfig is just a better fit here.
[The above btw. also makes "savedefconfig" less usefull].
More information about the Linuxppc-dev