Re: Documentation of kconfig language differs from implementationregarding existence of symbols

[Michal Marek]

Dne 10.10.2012 02:17, Martin Walch napsal(a):
> The file linux/Documentation/kbuild/kconfig-language.txt says:
> 
>> The following two methods produce the same kconfig symbol
>> dependencies but differ greatly in kconfig symbol existence
>> (production) in the generated config file.
>> 
>> case 1:
>> 
>> config FOO tristate "about foo" depends on BAR
>> 
>> vs. case 2:
>> 
>> if BAR config FOO tristate "about foo" endif
>> 
>> In case 1, the symbol FOO will always exist in the config file
>> (given no other dependencies).  In case 2, the symbol FOO will
>> only exist in the config file if BAR is enabled.
> 
> However, I can not reproduce this. The attached file contains both
> cases. When running make menuconfig, setting BAR0 and BAR1 both to
> n, and saving the configuration, there is neither FOO0 nor FOO1 in
> the resulting configuration file.

Indeed, that paragraph seems wrong. I think we should revert commit
64b81ed. Randy, Arnaud?

Thanks,
Michal

--
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/