ref-manual: clarify KCONFIG_MODE default behaviour

KCONFIG_MODE defaults to 'allnoconfig' when not set, regardless of whether
KBUILD_DEFCONFIG points to an in-tree or a meta-layer defconfig.

(From yocto-docs rev: f374b9c426f6c10710e011a4ad660231ee26efb8)

Signed-off-by: Carlos Sánchez de La Lama <csanchezdll@gmail.com>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Carlos Sánchez de La Lama 2025-05-28 20:15:24 +02:00 committed by Richard Purdie
parent be420892fe
commit 7b5409b811

View File

@ -5036,15 +5036,8 @@ system and gives an overview of their function and contents.
options not explicitly specified will be disabled in the kernel
config.
In case :term:`KCONFIG_MODE` is not set the behaviour will depend on where
the ``defconfig`` file is coming from. An "in-tree" ``defconfig`` file
will be handled in ``alldefconfig`` mode, a ``defconfig`` file placed
in ``${WORKDIR}`` through a meta-layer will be handled in
``allnoconfig`` mode.
An "in-tree" ``defconfig`` file can be selected via the
:term:`KBUILD_DEFCONFIG` variable. :term:`KCONFIG_MODE` does not need to
be explicitly set.
In case :term:`KCONFIG_MODE` is not set the ``defconfig`` file
will be handled in ``allnoconfig`` mode.
A ``defconfig`` file compatible with ``allnoconfig`` mode can be
generated by copying the ``.config`` file from a working Linux kernel