From: Bratiranjan Acharya <bratiranjan12@gmail.com>
To: Quentin Schulz <quentin.schulz@cherry.de>
Cc: yocto@lists.yoctoproject.org, Khem Raj <raj.khem@gmail.com>
Subject: Re: [yocto] Command line Variable
Date: Tue, 7 May 2024 15:49:18 +0530 [thread overview]
Message-ID: <CALSmAY6QmKUfa7Lse_hxFPOtqvu00027zvdQNw073q5UBxh9WA@mail.gmail.com> (raw)
In-Reply-To: <7daf5cfc-46de-4911-9848-171e7b675189@cherry.de>
[-- Attachment #1: Type: text/plain, Size: 1582 bytes --]
Hey Quentin,
I wanted to extend my gratitude for your assistance. I found the solution
in the Yocto manual, scripted accordingly, and after exporting, everything
is functioning smoothly now. Your help was greatly appreciated!
Thanks & Regards Brati
On Tue, 7 May 2024 at 15:24, Quentin Schulz <quentin.schulz@cherry.de>
wrote:
> Hi Brati,
>
>
> On 5/7/24 7:17 AM, Bratiranjan Acharya via lists.yoctoproject.org wrote:
> > Hello there! I've recently experimented with incorporating the following
> > lines into my recipe file:
> > BB_ENV_PASSTHROUGH_ADDITIONS = "BUILD_ID"
> > BUILD_ID ?= "none"
> > However, despite these additions, I encountered a persistent issue. Even
> > after executing the command "BUILD_ID=123456 bitbake custom-img" the
> value
> > of BUILD_ID consistently defaults to "none." I'm curious if there's an
> > alternative approach worth exploring. Any insights would be greatly
> > appreciated!
> >
>
>
> https://docs.yoctoproject.org/bitbake/2.8/bitbake-user-manual/bitbake-user-manual-ref-variables.html#term-BB_ENV_PASSTHROUGH_ADDITIONS
>
> """
> You must set this variable in the external environment in order for it
> to work.
> """
>
> So it needs to be outside any file from Bitbake, just have it in the
> shell environment before calling Bitbake.
>
> Also, this variable was name something different before Kirkstone so it
> depends on which version of Yocto you're using here, c.f.
>
> https://docs.yoctoproject.org/migration-guides/migration-4.0.html?highlight=bb_env_passthrough_additions#inclusive-language-improvements
>
> Cheers,
> Quentin
>
[-- Attachment #2: Type: text/html, Size: 2986 bytes --]
prev parent reply other threads:[~2024-05-07 10:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 4:24 Command line Variable Bratiranjan Acharya
2024-05-07 4:42 ` [yocto] " Khem Raj
2024-05-07 5:17 ` Bratiranjan Acharya
2024-05-07 9:54 ` Quentin Schulz
2024-05-07 10:19 ` Bratiranjan Acharya [this message]
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=CALSmAY6QmKUfa7Lse_hxFPOtqvu00027zvdQNw073q5UBxh9WA@mail.gmail.com \
--to=bratiranjan12@gmail.com \
--cc=quentin.schulz@cherry.de \
--cc=raj.khem@gmail.com \
--cc=yocto@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).