From: michael.opdenacker@bootlin.com
To: docs@lists.yoctoproject.org
Cc: Michael Opdenacker <michael.opdenacker@bootlin.com>,
Johan Bezem <jbezem.extern@arri.de>
Subject: [kirkstone][PATCH 3/8] ref-manual: variables: correct sdk installation default path
Date: Thu, 14 Mar 2024 10:13:53 +0100 [thread overview]
Message-ID: <20240314091358.84025-4-michael.opdenacker@bootlin.com> (raw)
In-Reply-To: <20240314091358.84025-1-michael.opdenacker@bootlin.com>
From: Michael Opdenacker <michael.opdenacker@bootlin.com>
From: Johan Bezem <jbezem.extern@arri.de>
The SDKPATH variable seems mistakenly identified as the
default path where the SDK will be installed by the generated
installation script, unless option '-d' or a manual input
overrides this default.
The intended variable is SDKPATHINSTALL. SDKPATH indicates
where the SDK is being composed and built.
The definitions have been added/updated.
Signed-off-by: Johan Bezem <jbezem.extern@arri.de>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
---
documentation/overview-manual/concepts.rst | 2 +-
documentation/ref-manual/variables.rst | 6 +++++-
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/documentation/overview-manual/concepts.rst b/documentation/overview-manual/concepts.rst
index 3e80d6fddd..a1fd3c4dad 100644
--- a/documentation/overview-manual/concepts.rst
+++ b/documentation/overview-manual/concepts.rst
@@ -1407,7 +1407,7 @@ This next list, shows the variables associated with a standard SDK:
Lists packages that make up the target part of the SDK (i.e. the part
built for the target hardware).
-- :term:`SDKPATH`: Defines the
+- :term:`SDKPATHINSTALL`: Defines the
default SDK installation path offered by the installation script.
- :term:`SDK_HOST_MANIFEST`:
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 691a0cdc1a..0887a40b6b 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -7201,6 +7201,10 @@ system and gives an overview of their function and contents.
configuration will not take effect.
:term:`SDKPATH`
+ Defines the path used to collect the SDK components and build the
+ installer.
+
+ :term:`SDKPATHINSTALL`
Defines the path offered to the user for installation of the SDK that
is generated by the OpenEmbedded build system. The path appears as
the default location for installing the SDK when you run the SDK's
@@ -7210,7 +7214,7 @@ system and gives an overview of their function and contents.
:term:`SDKTARGETSYSROOT`
The full path to the sysroot used for cross-compilation within an SDK
as it will be when installed into the default
- :term:`SDKPATH`.
+ :term:`SDKPATHINSTALL`.
:term:`SECTION`
The section in which packages should be categorized. Package
--
2.34.1
next prev parent reply other threads:[~2024-03-14 9:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 9:13 [kirkstone][PATCH 0/8] documentation backports michael.opdenacker
2024-03-14 9:13 ` [kirkstone][PATCH 1/8] ref-manual: tasks: do_cleanall: recommend using '-f' instead michael.opdenacker
2024-03-14 9:13 ` [kirkstone][PATCH 2/8] ref-manual: tasks: do_cleansstate: recommend using '-f' instead for a shared sstate michael.opdenacker
2024-03-14 9:13 ` michael.opdenacker [this message]
2024-03-14 9:13 ` [kirkstone][PATCH 4/8] ref-manual: variables: adding multiple groups in GROUPADD_PARAM michael.opdenacker
2024-03-14 9:13 ` [kirkstone][PATCH 5/8] dev-manual: packages: fix capitalization michael.opdenacker
2024-03-14 9:13 ` [kirkstone][PATCH 6/8] manuals: replace hyphens with em dashes michael.opdenacker
2024-03-14 9:13 ` [kirkstone][PATCH 7/8] contributor-guide: add notes for tests michael.opdenacker
2024-03-14 9:13 ` [kirkstone][PATCH 8/8] manuals: document VIRTUAL-RUNTIME variables 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=20240314091358.84025-4-michael.opdenacker@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=jbezem.extern@arri.de \
/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