From: Antonin Godard <antonin.godard@bootlin.com>
To: docs@lists.yoctoproject.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Antonin Godard <antonin.godard@bootlin.com>
Subject: [PATCH 1/5] sdk-manual/appendix-customizing-standard.rst: use code block for bitbake assignment
Date: Wed, 29 Jul 2026 12:02:24 +0200 [thread overview]
Message-ID: <20260729-sdk-clarifications-v1-1-661e65201bc7@bootlin.com> (raw)
In-Reply-To: <20260729-sdk-clarifications-v1-0-661e65201bc7@bootlin.com>
Use a code block for the DISTRO_FEATURES assignment instead of how it
appears as regular text currently.
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
documentation/sdk-manual/appendix-customizing-standard.rst | 11 ++++++-----
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/documentation/sdk-manual/appendix-customizing-standard.rst b/documentation/sdk-manual/appendix-customizing-standard.rst
index c619c15e4..90b73dc20 100644
--- a/documentation/sdk-manual/appendix-customizing-standard.rst
+++ b/documentation/sdk-manual/appendix-customizing-standard.rst
@@ -27,8 +27,9 @@ Adding API Documentation to the Standard SDK
You can include API documentation as well as any other documentation
provided by recipes with the standard SDK by adding "api-documentation"
-to the
-:term:`DISTRO_FEATURES`
-variable: DISTRO_FEATURES:append = " api-documentation" Setting this
-variable as shown here causes the OpenEmbedded build system to build the
-documentation and then include it in the standard SDK.
+to the :term:`DISTRO_FEATURES` variable::
+
+ DISTRO_FEATURES:append = " api-documentation"
+
+Setting this variable as shown here causes the OpenEmbedded build system to
+build the documentation and then include it in the standard SDK.
--
2.55.0
next prev parent reply other threads:[~2026-07-29 10:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 10:02 [PATCH 0/5] Make the SDK section not specific to the eSDK Antonin Godard
2026-07-29 10:02 ` Antonin Godard [this message]
2026-07-30 10:14 ` [docs] [PATCH 1/5] sdk-manual/appendix-customizing-standard.rst: use code block for bitbake assignment Quentin Schulz
2026-07-29 10:02 ` [PATCH 2/5] sdk-manual/intro.rst: remove a confusing sentence Antonin Godard
2026-07-30 10:21 ` [docs] " Quentin Schulz
2026-07-29 10:02 ` [PATCH 3/5] sdk-manual/intro.rst: link to sysroot term Antonin Godard
2026-07-30 10:24 ` [docs] " Quentin Schulz
2026-07-29 10:02 ` [PATCH 4/5] sdk-manual: rename the section to remove "extensible" Antonin Godard
2026-07-30 10:29 ` [docs] " Quentin Schulz
2026-07-31 8:56 ` Antonin Godard
2026-07-29 10:02 ` [PATCH 5/5] sdk-manual/intro.rst: detail differences between standard and extensible sysroots Antonin Godard
2026-07-30 11:39 ` [docs] " Quentin Schulz
2026-07-31 8:56 ` Antonin Godard
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=20260729-sdk-clarifications-v1-1-661e65201bc7@bootlin.com \
--to=antonin.godard@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=thomas.petazzoni@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