From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>,
Luca Ceresoli <luca.ceresoli@bootlin.com>
Subject: [PATCH 4/4] ref-manual: classes: kernel: document automatic defconfig usage
Date: Tue, 9 May 2023 14:40:38 +0200 [thread overview]
Message-ID: <20230509124038.2265185-4-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20230509124038.2265185-1-michael.opdenacker@bootlin.com>
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
From: Luca Ceresoli <luca.ceresoli@bootlin.com>
Since a very long time the kernel bbclass uses a defconfig file from
SRC_URI automatically. Document this feature.
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/ref-manual/classes.rst | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/documentation/ref-manual/classes.rst b/documentation/ref-manual/classes.rst
index de2d97de30..8f7cbf2b45 100644
--- a/documentation/ref-manual/classes.rst
+++ b/documentation/ref-manual/classes.rst
@@ -1532,6 +1532,13 @@ code to build all kernel trees. All needed headers are staged into the
:term:`STAGING_KERNEL_DIR` directory to allow out-of-tree module builds
using the :ref:`ref-classes-module` class.
+If a file named ``defconfig`` is listed in :term:`SRC_URI`, then by default
+:ref:`ref-tasks-configure` copies it as ``.config`` in the build directory,
+so it is automatically used as the kernel configuration for the build. This
+copy is not performed in case ``.config`` already exists there: this allows
+recipes to produce a configuration by other means in
+``do_configure:prepend``.
+
Each built kernel module is packaged separately and inter-module
dependencies are created by parsing the ``modinfo`` output. If all modules
are required, then installing the ``kernel-modules`` package installs all
--
2.34.1
next prev parent reply other threads:[~2023-05-09 12:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 12:40 [PATCH 1/4] [mickledore] migration-guides: release-notes-4.2: add doc improvement highlights michael.opdenacker
2023-05-09 12:40 ` [PATCH 2/4] [mickledore] release-notes-4.2: update known issues and Repositories/Downloads michael.opdenacker
2023-05-09 12:40 ` [PATCH 3/4] ref-manual: classes: kernel: remove incorrect sentence opening michael.opdenacker
2023-05-09 12:40 ` michael.opdenacker [this message]
[not found] ` <175D7A12A151A6F9.26836@lists.yoctoproject.org>
2023-05-09 12:45 ` [docs] [PATCH 4/4] ref-manual: classes: kernel: document automatic defconfig usage Michael Opdenacker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230509124038.2265185-4-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=luca.ceresoli@bootlin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox