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 2/5] sdk-manual/intro.rst: remove a confusing sentence
Date: Wed, 29 Jul 2026 12:02:25 +0200 [thread overview]
Message-ID: <20260729-sdk-clarifications-v1-2-661e65201bc7@bootlin.com> (raw)
In-Reply-To: <20260729-sdk-clarifications-v1-0-661e65201bc7@bootlin.com>
I have a hard time understanding the meaning of this sentence at this
point in the manual. populate_sdk and populate_sdk_ext are best known as
tasks, so the meaning for them as "archives" is unclear.
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
documentation/sdk-manual/intro.rst | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/documentation/sdk-manual/intro.rst b/documentation/sdk-manual/intro.rst
index dd2902cc4..3e78219fc 100644
--- a/documentation/sdk-manual/intro.rst
+++ b/documentation/sdk-manual/intro.rst
@@ -35,9 +35,7 @@ destined to run on some target machine. SDKs are completely
self-contained. The binaries are linked against their own copy of
``libc``, which results in no dependencies on the target system. To
achieve this, the pointer to the dynamic loader is configured at install
-time since that path cannot be dynamically altered. This is the reason
-for a wrapper around the ``populate_sdk`` and ``populate_sdk_ext``
-archives.
+time since that path cannot be dynamically altered.
Another feature of the SDKs is that only one set of cross-compiler
toolchain binaries are produced for any given architecture. This feature
--
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 ` [PATCH 1/5] sdk-manual/appendix-customizing-standard.rst: use code block for bitbake assignment Antonin Godard
2026-07-30 10:14 ` [docs] " Quentin Schulz
2026-07-29 10:02 ` Antonin Godard [this message]
2026-07-30 10:21 ` [docs] [PATCH 2/5] sdk-manual/intro.rst: remove a confusing sentence 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-2-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.