From: "Bezem, Johan (extern)" <JBezem.extern@arri.de>
To: "michael.opdenacker@bootlin.com" <michael.opdenacker@bootlin.com>
Cc: "docs@lists.yoctoproject.org" <docs@lists.yoctoproject.org>
Subject: Re: [docs] [PATCH] variables.rst: SDKPATHINSTALL correct installation default path
Date: Fri, 23 Feb 2024 10:59:44 +0000 [thread overview]
Message-ID: <PR3PR07MB824382E96561F0F922CFC445FC552@PR3PR07MB8243.eurprd07.prod.outlook.com> (raw)
Hi Michael,
As I'm not all that familiar (yet) with Yocto and BitBake, I need to carefully
research the variable SDKPATH, especially since the documentation is apparently incorrect.
And it's not my highest priority. So if you have the time, any help is welcome.
Rgds,
Johan
-----Ursprüngliche Nachricht-----
Von: docs@lists.yoctoproject.org <docs@lists.yoctoproject.org> Im Auftrag von Michael Opdenacker via lists.yoctoproject.org
Gesendet: Freitag, 23. Februar 2024 11:20
An: Bezem, Johan (extern) <JBezem.extern@arri.de>
Cc: docs@lists.yoctoproject.org
Betreff: Re: [docs] [PATCH] variables.rst: SDKPATHINSTALL correct installation default path
Hi Yohan
On 2/14/24 at 10:31, Michael Opdenacker wrote:
> Hi Johan
>
> Thanks for pointing this out!
>
> On 2/13/24 at 13:52, Bezem, Johan (extern) wrote:
>> 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
>
>
> I believe we should also keep SDKPATH as it's still used in some
> recipes in Poky. Could you describe it's current usage too?
>
> Another thing is that you should also update
> documentation/overview-manual/concepts.rst which refers to SDKPATH,
> and the description of SDKTARGETSYSROOT too.
>
> You could have caught this by running "make html":
> .../yocto-docs/documentation/overview-manual/concepts.rst:1378:
> WARNING: term not in glossary: 'SDKPATH'
> .../yocto-docs/documentation/ref-manual/variables.rst:7617: WARNING:
> term not in glossary: 'SDKPATH'
>
> Could you send an update?
Do you need help doing this? I'll be happy to help if you don't have time right now.
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next reply other threads:[~2024-02-23 10:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 10:59 Bezem, Johan (extern) [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-28 13:04 [docs] [PATCH] variables.rst: SDKPATHINSTALL correct installation default path Bezem, Johan (extern)
2024-02-26 16:15 Johan Bezem
2024-02-29 11:20 ` [docs] " Michael Opdenacker
2024-02-13 12:52 Johan Bezem
2024-02-14 9:31 ` [docs] " Michael Opdenacker
2024-02-23 10:19 ` 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=PR3PR07MB824382E96561F0F922CFC445FC552@PR3PR07MB8243.eurprd07.prod.outlook.com \
--to=jbezem.extern@arri.de \
--cc=docs@lists.yoctoproject.org \
--cc=michael.opdenacker@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).