Re: [docs] [PATCH 5/5] sdk-manual/intro.rst: detail differences between standard and extensible sysroots
Quentin Schulz <[email protected]> Thu, 30 Jul 2026 13:39:46 +0200
| Newsgroups | org.yoctoproject.lists.docs |
|---|---|
| Message-ID | <[email protected]> |
Hi Antonin, On 7/29/26 12:02 PM, 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] > > Signed-off-by: Antonin Godard <[email protected]> > --- > documentation/sdk-manual/intro.rst | 15 +++++++++++++++ > 1 file changed, 15 insertions(+) > > diff --git a/documentation/sdk-manual/intro.rst b/documentation/sdk-manual/intro.rst > index 8ccbcfa20..2e5f73f0b 100644 > --- a/documentation/sdk-manual/intro.rst > +++ b/documentation/sdk-manual/intro.rst > @@ -123,6 +123,21 @@ 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 sysroot differ in content: > + Why did we stop referring to the Sysroot term (:term:`Sysroot`)? > +- The standard SDK sysroot only contains libraries and headers for the packages s/for/of/? I think we should also mention this brings the libraries and headers of their dependencies (recursively) as well? > + found in the :term:`TOOLCHAIN_TARGET_TASK` and :term:`TOOLCHAIN_HOST_TASK` > + definitions, for the target and native sysroots respectively. > + I know we have a nativesdk OVERRIDE, so is it still a native/target sysroot or should it be named nativesdk too (I've never built an SDK so I don't know). > + See :doc:`/sdk-manual/appendix-customizing-standard` to learn how to > + customize it. > + > +- The extensible SDK sysroot is completely managed by the ``devtool`` Can we maybe point at some docs for devtool? From a quick grep, maybe something in documentation/ref-manual/devtool-reference.rst? > + command-line tool, and its content is the same as the sysroot of the image > + recipe for which the SDK was built. > + I guess we could show how to do this here? I think it should be something like: bitbake my-image -c populate_sdk (or maybe point at https://docs.yoctoproject.org/sdk-manual/appendix-obtain.html#building-an-sdk-installer ?). > + See :doc:`/sdk-manual/appendix-customizing` to learn how to customize it. > + Thinking about it, we probably should update documentation/ref-manual/terms.rst for the Sysroot entry in the glossary to explain sysroot for the SDKs (or at the very least point at the section here). Cheers, Quentin