[PATCH v2 0/5] Make the SDK section not specific to the eSDK

[PATCH v2 0/5] Make the SDK section not specific to the eSDK

[Antonin Godard]

While the content of the SDK section covers both the standard and the
extensible SDKs, the title only referred to the extensible SDK which is
confusing.

This series comes with other various patches to improve this section.

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
Changes in v2:
- Apply suggestions from Quentin (thanks!)
- Link to v1: https://patch.msgid.link/20260729-sdk-clarifications-v1-0-661e65201bc7@bootlin.com

---
Antonin Godard (5):
      sdk-manual/appendix-customizing-standard.rst: use code block for bitbake assignment
      sdk-manual/intro.rst: remove a confusing sentence
      sdk-manual/intro.rst: link to sysroot term
      sdk-manual: rename the section to remove "extensible"
      sdk-manual/intro.rst: detail differences between standard and extensible sysroots

 documentation/index.rst                            |  2 +-
 .../sdk-manual/appendix-customizing-standard.rst   | 11 +++----
 documentation/sdk-manual/index.rst                 |  6 ++--
 documentation/sdk-manual/intro.rst                 | 35 ++++++++++++++++------
 4 files changed, 36 insertions(+), 18 deletions(-)
---
base-commit: 41dae3c3da3ada1745fc60228ff6269c64ee2361
change-id: 20260529-sdk-clarifications-9aab0fa9a60e

[PATCH v2 1/5] sdk-manual/appendix-customizing-standard.rst: use code block for bitbake assignment

[Antonin Godard]

Use a code block for the DISTRO_FEATURES assignment instead of how it
appears as regular text currently.

Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
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

[PATCH v2 2/5] sdk-manual/intro.rst: remove a confusing sentence

[Antonin Godard]

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.

Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
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

[PATCH v2 3/5] sdk-manual/intro.rst: link to sysroot term

[Antonin Godard]

Link to the definition of a sysroot (from our glossary) when it is first
introduced and later in the "Sysroots" section.

Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/sdk-manual/intro.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/documentation/sdk-manual/intro.rst b/documentation/sdk-manual/intro.rst
index 3e78219fc..53246bd9a 100644
--- a/documentation/sdk-manual/intro.rst
+++ b/documentation/sdk-manual/intro.rst
@@ -45,7 +45,7 @@ environment script and contained in variables such as
 :term:`CC` and
 :term:`LD`. This reduces the space needed
 for the tools. Understand, however, that every target still needs its own
-sysroot because those binaries are target-specific.
+:term:`sysroot` because those binaries are target-specific.
 
 The SDK development environment consists of the following:
 
@@ -117,7 +117,7 @@ cross-toolchain works with a matching target sysroot.
 Sysroots
 --------
 
-The native and target sysroots contain needed headers and libraries for
+The native and target :term:`sysroots <Sysroot>` contain needed headers and libraries for
 generating binaries that run on the target architecture. The target
 sysroot is based on the target root filesystem image that is built by
 the OpenEmbedded build system and uses the same metadata configuration

-- 
2.55.0

[PATCH v2 4/5] sdk-manual: rename the section to remove "extensible"

[Antonin Godard]

The SDK manual covers both the standard and extensible SDKs yet the
title does not imply that, so rename the section to "Yocto Project
Application Development and the Software Development Kit (SDK) Manual".

As a consequence, rename the first section title and reword the intro.

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/index.rst            | 2 +-
 documentation/sdk-manual/index.rst | 6 +++---
 documentation/sdk-manual/intro.rst | 8 ++++----
 3 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/documentation/index.rst b/documentation/index.rst
index afabb6615..24a6802a4 100644
--- a/documentation/index.rst
+++ b/documentation/index.rst
@@ -67,7 +67,7 @@ infrastructure.
    Linux Kernel Development Manual <kernel-dev/index>
    Security Manual <security-manual/index>
    Profile and Tracing Manual <profile-manual/index>
-   Application Development and the Extensible SDK (eSDK) <sdk-manual/index>
+   Application Development and SDKs Manual <sdk-manual/index>
    Toaster Manual <toaster-manual/index>
    Test Environment Manual <test-manual/index>
    BitBake User Manual <bitbake>
diff --git a/documentation/sdk-manual/index.rst b/documentation/sdk-manual/index.rst
index dc7186b91..a5c35caba 100644
--- a/documentation/sdk-manual/index.rst
+++ b/documentation/sdk-manual/index.rst
@@ -1,8 +1,8 @@
 .. SPDX-License-Identifier: CC-BY-SA-2.0-UK
 
-========================================================================================
-Yocto Project Application Development and the Extensible Software Development Kit (eSDK)
-========================================================================================
+=====================================================================================
+Yocto Project Application Development and Software Development Kits (SDK/eSDK) Manual
+=====================================================================================
 
 |
 
diff --git a/documentation/sdk-manual/intro.rst b/documentation/sdk-manual/intro.rst
index 53246bd9a..b78248d54 100644
--- a/documentation/sdk-manual/intro.rst
+++ b/documentation/sdk-manual/intro.rst
@@ -4,11 +4,11 @@
 Introduction
 ************
 
-eSDK Introduction
-=================
+SDK/eSDK Introduction
+=====================
 
-Welcome to the Yocto Project Application Development and the Extensible
-Software Development Kit (eSDK) manual. This manual
+Welcome to the Yocto Project Application Development and
+Software Development Kits (SDK/eSDK) manual. This manual
 explains how to use both the Yocto Project extensible and standard
 SDKs to develop applications and images.
 

-- 
2.55.0

Re: [docs] [PATCH v2 4/5] sdk-manual: rename the section to remove "extensible"

[Quentin Schulz]

Hi Antonin,

On 7/31/26 11:19 AM, Antonin Godard via lists.yoctoproject.org wrote:
> The SDK manual covers both the standard and extensible SDKs yet the
> title does not imply that, so rename the section to "Yocto Project
> Application Development and the Software Development Kit (SDK) Manual".
> 
> As a consequence, rename the first section title and reword the intro.
> 

Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>

Thanks!
Quentin

[PATCH v2 5/5] sdk-manual/intro.rst: detail differences between standard and extensible sysroots

[Antonin Godard]

The sysroot in the standard and the extensible SDKs are managed
differently. Detail this in the Sysroots section.

[YOCTO #14830]

Signed-off-by: Antonin Godard <antonin.godard@bootlin.com>
---
 documentation/sdk-manual/intro.rst | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/documentation/sdk-manual/intro.rst b/documentation/sdk-manual/intro.rst
index b78248d54..c8fa8d619 100644
--- a/documentation/sdk-manual/intro.rst
+++ b/documentation/sdk-manual/intro.rst
@@ -123,6 +123,25 @@ sysroot is based on the target root filesystem image that is built by
 the OpenEmbedded build system and uses the same metadata configuration
 used to build the cross-toolchain.
 
+However, the extensible and standard SDKs :term:`sysroots <Sysroot>` differ in content:
+
+-  The standard SDK :term:`sysroot` only contains libraries and headers for the packages
+   --- and their dependencies --- found in the :term:`TOOLCHAIN_TARGET_TASK`
+   and :term:`TOOLCHAIN_HOST_TASK` definitions, for the target and host
+   :term:`sysroots <sysroot>` respectively.
+
+   See :doc:`/sdk-manual/appendix-obtain` to learn how to build it and
+   :doc:`/sdk-manual/appendix-customizing-standard` to learn how to customize
+   it.
+
+-  The extensible SDK :term:`sysroot` is completely managed by the :doc:`devtool
+   </ref-manual/devtool-reference>` command-line tool, and its content is the
+   same as the :term:`sysroot` of the image recipe for which the SDK was built.
+
+   See :doc:`/sdk-manual/appendix-obtain` to learn how to build it and
+   :doc:`/sdk-manual/appendix-customizing` to learn how to customize
+   it.
+
 The QEMU Emulator
 -----------------
 

-- 
2.55.0

Re: [docs] [PATCH v2 5/5] sdk-manual/intro.rst: detail differences between standard and extensible sysroots

[Quentin Schulz]

Hi Antonin,

On 7/31/26 11:19 AM, Antonin Godard via lists.yoctoproject.org wrote:
> The sysroot in the standard and the extensible SDKs are managed
> differently. Detail this in the Sysroots section.
> 
> [YOCTO #14830]
> 

Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>

Thanks!
Quentin

Re: [PATCH v2 0/5] Make the SDK section not specific to the eSDK

[Antonin Godard]

Applied, thanks!

[1/5] sdk-manual/appendix-customizing-standard.rst: use code block for bitbake assignment
      commit: 99768ead76777c12d48f5b00e9d21808c3d2642a
[2/5] sdk-manual/intro.rst: remove a confusing sentence
      commit: 21c43225d6775887ea4b85531afb7c08a550e7b6
[3/5] sdk-manual/intro.rst: link to sysroot term
      commit: 084f1f14cdbb04c5cbb520b29d2aea78c309a624
[4/5] sdk-manual: rename the section to remove "extensible"
      commit: 537f079c14744216cea8cad615df2ea469ef0182
[5/5] sdk-manual/intro.rst: detail differences between standard and extensible sysroots
      commit: 17454b7565f15325b2805717167451a9a13427a7