Our usage of the Kconfig language so far is just the tip of the proverbial iceberg. The fact is, the kbuild system uses the Kconfig language (or syntax) to express and create menus using simple ASCII text directives. The language includes menu entries, attributes, (reverse) dependencies, visibility constraints, help text, and so on.
The kernel documents the Kconfig language constructs and syntax here: https://www.kernel.org/doc/Documentation/kbuild/kconfig-language.txt. Do refer to this document for complete details.
A brief (and incomplete) mention of the more common Kconfig constructs is given in the following table:
|
Construct |
Meaning |
|
config <FOO> |
Specifies the menu entry name (of the form CONFIG_FOO) here; just put the FOO part. |
|
Menu attributes |
|
|
bool ["<description>"] |
Specifies the config option as a Boolean; its value in .config will be either Y (built into the kernel... |
