From: Johan Bezem <jbezem.extern@arri.de>
To: <docs@lists.yoctoproject.org>
Cc: "Bezem, Johan" <jbezem.extern@arri.de>
Subject: [PATCH] variables.rst: SDKPATHINSTALL correct installation default path
Date: Tue, 13 Feb 2024 13:52:18 +0100 [thread overview]
Message-ID: <20240213125218.5480-1-jbezem.extern@arri.de> (raw)
From: "Bezem, Johan" <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.
From what I understood from the various sources, the intended
variable is SDKPATHINSTALL.
I have tried overriding both SDKPATH and SDKPATHINSTALL
(separately), and only overriding the latter had the intended
effect and was successful.
Signed-off-by: Johan Bezem <jbezem.extern@arri.de>
---
documentation/ref-manual/variables.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 6f7d6ff01..f292b8dad 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -7611,7 +7611,7 @@ system and gives an overview of their function and contents.
variable in your distribution configuration file. If you do, the
configuration will not take effect.
- :term:`SDKPATH`
+ :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
--
2.30.2
next reply other threads:[~2024-02-13 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 12:52 Johan Bezem [this message]
2024-02-14 9:31 ` [docs] [PATCH] variables.rst: SDKPATHINSTALL correct installation default path Michael Opdenacker
2024-02-23 10:19 ` Michael Opdenacker
-- strict thread matches above, loose matches on Subject: below --
2024-02-26 16:15 Johan Bezem
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=20240213125218.5480-1-jbezem.extern@arri.de \
--to=jbezem.extern@arri.de \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).