Question about some Kconfig dependencies

[Sarah Nadi]

Hi,

I am a researcher at the University of Waterloo in Canada. We are 
currently working on reverse engineering variability/feature models from 
code by extracting configuration constraints through static analyses 
(e.g., checking for conditional parsing, type, or linker errors). We 
compare existing configuration constraints in Kconfig to those we 
extract. Our analysis can automatically recover 65% of the dependencies 
in Kconfig by analyzing the code. We are currently investigating the 
Kconfig dependencies which we could not automatically extract, but we 
could not find obvious explanations for some of them.

For example, can someone provide us some insight about the reason behind 
the following dependencies:


Why does FEATURE_INDIVIDUAL depend on BUILD_LIBBUSYBOX. Is there a 
technical dependency in the code which makes this dependency necessary?

Why does FEATURE_USERNAME_COMPLETION depend on FEATURE_TAB_COMPLETION in 
the libbb folder? I think you can successfully compile Busybox by just 
selecting FEATURE_USERNAME_COMPLETION without FEATURE_TAB_COMPLETION 
(after removing the dependency from Config.in).

Thanks,
Sarah Nadi