From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>,
Paul Eggleton <bluelightning@bluelightning.org>
Subject: [kirkstone][PATCH 5/7] ref-manual: update SDK_NAME variable documentation
Date: Tue, 14 Nov 2023 17:49:40 +0100 [thread overview]
Message-ID: <20231114164942.133472-6-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20231114164942.133472-1-michael.opdenacker@bootlin.com>
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
From: Paul Eggleton <bluelightning@bluelightning.org>
Update for changes in nanbield. Note that I am documenting what is set
by poky.conf here (since this is Yocto Project documentation), which is
slightly different from what is done in meta/conf/bitbake.conf.
Signed-off-by: Paul Eggleton <bluelightning@bluelightning.org>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/ref-manual/variables.rst | 17 ++++++++++-------
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index a75581f2fd..5163abf559 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -6880,13 +6880,16 @@ system and gives an overview of their function and contents.
:term:`SDK_EXT_TYPE` is set to "full".
:term:`SDK_NAME`
- The base name for SDK output files. The name is derived from the
- :term:`DISTRO`, :term:`TCLIBC`,
- :term:`SDK_ARCH`,
- :term:`IMAGE_BASENAME`, and
- :term:`TUNE_PKGARCH` variables::
-
- SDK_NAME = "${DISTRO}-${TCLIBC}-${SDK_ARCH}-${IMAGE_BASENAME}-${TUNE_PKGARCH}"
+ The base name for SDK output files. The default value (as set in
+ ``meta-poky/conf/distro/poky.conf``) is derived from the
+ :term:`DISTRO`,
+ :term:`TCLIBC`,
+ :term:`SDKMACHINE`,
+ :term:`IMAGE_BASENAME`,
+ :term:`TUNE_PKGARCH`, and
+ :term:`MACHINE` variables::
+
+ SDK_NAME = "${DISTRO}-${TCLIBC}-${SDKMACHINE}-${IMAGE_BASENAME}-${TUNE_PKGARCH}-${MACHINE}"
:term:`SDK_OS`
Specifies the operating system for which the SDK will be built. The
--
2.34.1
next prev parent reply other threads:[~2023-11-14 16:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 16:49 [kirkstone][PATCH 0/7] kirkstone backports michael.opdenacker
2023-11-14 16:49 ` [kirkstone][PATCH 1/7] ref-manual: variables: document OEQA_REPRODUCIBLE_* variables michael.opdenacker
2023-11-14 16:49 ` [kirkstone][PATCH 2/7] ref-manual: variables: mention new CDN for SSTATE_MIRRORS michael.opdenacker
2023-11-14 16:49 ` [kirkstone][PATCH 3/7] ref-manual: variables: add RECIPE_MAINTAINER michael.opdenacker
2023-11-14 16:49 ` [kirkstone][PATCH 4/7] overview-manual: concepts: Add Bitbake Tasks Map michael.opdenacker
2023-11-14 16:49 ` michael.opdenacker [this message]
2023-11-14 16:49 ` [kirkstone][PATCH 6/7] ref-manual: classes: explain cml1 class name michael.opdenacker
2023-11-14 16:49 ` [kirkstone][PATCH 7/7] manuals: update class references michael.opdenacker
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=20231114164942.133472-6-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=bluelightning@bluelightning.org \
--cc=docs@lists.yoctoproject.org \
/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