From: Quentin Schulz <quentin.schulz@cherry.de>
To: antonin.godard@bootlin.com, docs@lists.yoctoproject.org
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [docs] [PATCH 1/3] overview-manual/yp-intro.rst: fix SDK type in bullet list
Date: Wed, 14 Jan 2026 11:01:12 +0100 [thread overview]
Message-ID: <6248e54e-d7c6-4658-8f99-e02188cf0aa8@cherry.de> (raw)
In-Reply-To: <20260105-update-workflow-diagram-v1-1-fc1c6f402064@bootlin.com>
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
next prev parent reply other threads:[~2026-01-14 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 16:02 [PATCH 0/3] Convert YP flow diagram to SVG Antonin Godard
2026-01-05 16:02 ` [PATCH 1/3] overview-manual/yp-intro.rst: fix SDK type in bullet list Antonin Godard
2026-01-14 10:01 ` Quentin Schulz [this message]
2026-01-05 16:02 ` [PATCH 2/3] overview-manual: convert YP-flow-diagram.png to SVG Antonin Godard
2026-01-05 16:02 ` [PATCH 3/3] Remove diagrams directory 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=6248e54e-d7c6-4658-8f99-e02188cf0aa8@cherry.de \
--to=quentin.schulz@cherry.de \
--cc=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