On Tue, Jul 20, 2010 at 04:37:06AM +1000, Stephen Rothwell wrote:
> This is a fairly brute force approach to allowing a Kconfig "select"
> to specify an excplicit value for the selected config sybmol.
>
> The syntax of select is changed to:
>
> "select" <symbol> [<expr>] ["if" expr]
>
> The approach taken is to add a list of <value, dependency expression>
> pairs to the symbol and check them whenever the reverse depends (from
> a current-style select) are checked.
I do not see the need for this feature.
I have read most of the postings in the defconfig battle and
I saw Linus' select suggestion.
But we can do almost all of this today (or tomorrow).
Consider following Kconfig file:
config USB_SUPPORT
def_bool n
config NET
def_bool y
source arch/x86/Kconfig
We use the feature that we can specify the same
config option several times.
And the first default value that is "visible"
will be used.
So it allows us to enable and disable any option.
And if we for example want to set a specific LOG_BUF_SHIFT
we use the same trick:
config LOG_BUF_SHIFT
int
default 14
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.
So with alldefconfig I think we have all the features we need
to create sensible default configs in the Kconfig language.
And therefore I do not see the need for the extension to select.
For the same reason I did not look closer at the implementation.
Sam
--
To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
