On 29 July 2010 11:16, Sam Ravnborg <sam@xxxxxxxxxxxx> wrote: > On Thu, Jul 29, 2010 at 11:01:43AM +0200, Vegard Nossum wrote: >> Hi, >> >> Consider the following kconfig fragment: >> >> config A >> >> if A >> config B >> endif > > The dependencies control the visibility. > The try to explain this consider this adopted > Kconfig file fragment: > > config A > bool "A" > > config B > bool "B" > > if A > config B > prompt "BB" > endif > > > See how B shows up in two places with different dependencies. > Therefore dependencies are an attribute of the menu - not the symbol. > > So to properly inspect dependencies you need to traverse the menus, > not the symbols as they may be used in several places. Hm, wow, thanks for the explanation, that helps a lot. There is still just one symbol "B", right, but it has two prompts? (And each prompt/menu has a different set of dependencies.) Can the two prompts have different "depends on"-dependencies, or are the following two definitions exactly equivalent? 1) config C depends on A depends on B 2) config C depends on A config C depends on B Thanks again, Vegard -- 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
