From: "Tom Rini" <tom.rini@gmail.com>
To: docs@lists.yoctoproject.org
Subject: [PATCH 1/3] common-tasks: Add a summary to the end of the bbappend example
Date: Thu, 12 Aug 2021 12:10:25 -0400 [thread overview]
Message-ID: <20210812161027.580-1-trini@konsulko.com> (raw)
Try and make it clearer what the final result of this bbappend example
is.
Signed-off-by: Tom Rini <trini@konsulko.com>
---
documentation/dev-manual/common-tasks.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/documentation/dev-manual/common-tasks.rst b/documentation/dev-manual/common-tasks.rst
index 37077d72d451..2d8ef96e2600 100644
--- a/documentation/dev-manual/common-tasks.rst
+++ b/documentation/dev-manual/common-tasks.rst
@@ -545,6 +545,12 @@ important as it ensures that items in the list remain colon-separated.
allow to add build options (e.g. ``systemd``). For these cases, your
append file would not even use the :term:`FILESEXTRAPATHS` statement.
+The end result of this ``.bbappend`` file is that on a Raspberry Pi, where
+``rpi`` will exist in the list of :term:`OVERRIDES`, the file
+``meta-raspberrypi/recipes-bsp/formfactor/formfactor/rpi/machconfig`` will be
+used during ``do_fetch`` and the test for a non-zero file size in
+``do_install`` will return true, and the file will be installed.
+
Prioritizing Your Layer
-----------------------
--
2.17.1
next reply other threads:[~2021-08-12 16:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 16:10 Tom Rini [this message]
2021-08-12 16:10 ` [PATCH 2/3] manuals: Rename the "Using .bbappend Files in Your Layer" section Tom Rini
2021-08-13 8:29 ` [docs] " Quentin Schulz
2021-08-13 9:12 ` Michael Opdenacker
2021-08-12 16:10 ` [PATCH 3/3] common-tasks: Add an example of using bbappends to add a file Tom Rini
2021-08-13 8:27 ` [docs] " Quentin Schulz
2021-08-13 9:15 ` Michael Opdenacker
2021-08-13 14:40 ` Tom Rini
2021-08-13 15:13 ` Tom Rini
2021-08-13 8:16 ` [docs] [PATCH 1/3] common-tasks: Add a summary to the end of the bbappend example Michael Opdenacker
2021-08-13 8:21 ` Quentin Schulz
2021-08-13 8:28 ` Michael Opdenacker
2021-08-13 8:31 ` Quentin Schulz
2021-08-13 8:48 ` 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=20210812161027.580-1-trini@konsulko.com \
--to=tom.rini@gmail.com \
--cc=docs@lists.yoctoproject.org \
/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