diff mbox series

[1/3] overview-manual/yp-intro.rst: fix SDK type in bullet list

Message ID 20260105-update-workflow-diagram-v1-1-fc1c6f402064@bootlin.com
State Accepted
Headers show
Series Convert YP flow diagram to SVG | expand

Commit Message

Antonin Godard Jan. 5, 2026, 4:02 p.m. UTC
The YP generates an SDK by default, which can be meta-toolchain, an
image-specific one, or an extensible SDK (eSDK). Don't be specific in
this bullet list.

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

Comments

Quentin Schulz Jan. 14, 2026, 10:01 a.m. UTC | #1
Hi Antonin,

On 1/5/26 5:02 PM, Antonin Godard via lists.yoctoproject.org wrote:
> The YP generates an SDK by default, which can be meta-toolchain, an

What do you mean "by default"?

> image-specific one, or an extensible SDK (eSDK). Don't be specific in
> this bullet list.
> 

Isn't "for application development in parallel" actually specific? I'm 
assuming most people will not use a normal SDK but an eSDK for 
developing software as the normal SDK is (as I understood it) a minimal 
toolchain which won't contain most of what people would expect (headers 
for packages found in an image for example).

When I bake an image, I don't get an SDK automatically no? According to 
the docs, I need to run -c populate_sdk/populate_sdk_ext for this to 
happen? c.f. 
https://docs.yoctoproject.org/sdk-manual/appendix-obtain.html#building-an-sdk-installer

The docs were also very confusing as that is explained **after** how to 
use the SDK and in the sections we just say "run the script"... but 
where do we generate the script, where do we get it from?

Cheers,
Quentin
diff mbox series

Patch

diff --git a/documentation/overview-manual/yp-intro.rst b/documentation/overview-manual/yp-intro.rst
index dc4d5125d..5cc39b31b 100644
--- a/documentation/overview-manual/yp-intro.rst
+++ b/documentation/overview-manual/yp-intro.rst
@@ -762,7 +762,8 @@  Here is a brief summary of the "workflow":
    package feed that is used to create the final root file image.
 
 #. The build system generates the file system image and a customized
-   Extensible SDK (eSDK) for application development in parallel.
+   :doc:`SDK </sdk-manual/index>` (Software Development Kit) for application
+   development in parallel.
 
 For a very detailed look at this workflow, see the
 ":ref:`overview-manual/concepts:openembedded build system concepts`" section.