2 added 364 characters in body
source | link

make menuconfig doesn't dynamically determine your environment and tries to set the appropriate config but uses your .config file and the default entries in kconfig.

So yes the defaults come with the source and are specified in the kconfig files which also specify the help text, dependencies and other things. Have a look at a sample kconfig file like net/Kconfig.

make localmodconfig on the other hand tries to create a custom tailored kernel configuration for your system based on the loaded modules. It takes your current configuration (typically from your distribution) and will only enable the loaded modules.

make menuconfig doesn't dynamically determine your environment and tries to set the appropriate config but uses your .config file and the default entries in kconfig.

So yes the defaults come with the source and are specified in the kconfig files which also specify the help text, dependencies and other things. Have a look at a sample kconfig file like net/Kconfig.

make menuconfig doesn't dynamically determine your environment and tries to set the appropriate config but uses your .config file and the default entries in kconfig.

So yes the defaults come with the source and are specified in the kconfig files which also specify the help text, dependencies and other things. Have a look at a sample kconfig file like net/Kconfig.

make localmodconfig on the other hand tries to create a custom tailored kernel configuration for your system based on the loaded modules. It takes your current configuration (typically from your distribution) and will only enable the loaded modules.

1
source | link

make menuconfig doesn't dynamically determine your environment and tries to set the appropriate config but uses your .config file and the default entries in kconfig.

So yes the defaults come with the source and are specified in the kconfig files which also specify the help text, dependencies and other things. Have a look at a sample kconfig file like net/Kconfig.