Messages in this thread | | | Date | Tue, 22 Dec 2009 12:44:14 +0000 | From | "Jan Beulich" <> | Subject | Kconfig choice oddities? |
| |
Sam, Roman,
what is the reason for the difference in behavior between choices' and simple options' prompts followed by conditionals? For simple options, the conditional, if evaluating to false, just hides the prompt (forcing the default to be used), but for choices it seems to eliminate the choice altogether (i.e. it appears to have the same effect as a "depends on").
Further, is it really appropriate to write out the settings of all choice members, even those that have dependencies evaluating to false? The effect of this is that when the dependencies change, resulting in a new choice member to become visible, "make oldconfig" doesn't present the choice to the user since a "selected" value was already read from .config.
Thanks, Jan
| |