From: Gyorgy Sarvari <skandigraun@gmail.com>
To: yocto@lists.yoctoproject.org, joseph.maniaci@seagate.com,
Quentin Schulz <quentin.schulz@cherry.de>
Subject: Re: [yocto] Environmental variable present in do_compile() {}, bitbake recipe -e, but is missing from do_configure() {} #bitbake
Date: Thu, 17 Jul 2025 19:20:21 +0200 [thread overview]
Message-ID: <7cc556c6-d347-469a-9ecd-47949e492aed@gmail.com> (raw)
In-Reply-To: <29250.1752770915071927700@lists.yoctoproject.org>
On 7/17/25 18:48, joseph.maniaci via lists.yoctoproject.org wrote:
> Ah, I'm using a script to do this in a repeatable fashion, so I forgot
> that the last thing it does is
>
> export BB_ENV_PASSTHROUGH_ADDITIONS="$BB_ENV_PASSTHROUGH_ADDITIONS
> ABC"
>
This makes the variable available in the bitbake datastore (e.g. you can
reference it in recipes, or you can use d.getVar("ABC") in python), but
it won't make it available automatically as an environment variable. To
have it as an env var you are expected to export it, with "export ABC"
in the recipe, either in a task to make it available in that specific
task, or outside of tasks, to make it available in all tasks. (Or in a
global config file, like local.conf for example, to make it available
for all tasks globally as env var)
Since you mention that it is available in the compile step, I wonder if
you have an explicit "export ABC" in the do_compile task.
next prev parent reply other threads:[~2025-07-17 17:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 21:20 Environmental variable present in do_compile() {}, bitbake recipe -e, but is missing from do_configure() {} #bitbake joseph.maniaci
2025-07-17 9:46 ` [yocto] " Alexander Kanavin
2025-07-17 16:24 ` joseph.maniaci
2025-07-17 16:29 ` Quentin Schulz
2025-07-17 16:48 ` joseph.maniaci
2025-07-17 17:20 ` Gyorgy Sarvari [this message]
2025-07-17 17:28 ` joseph.maniaci
2025-07-17 18:16 ` joseph.maniaci
2025-07-18 7:43 ` Gyorgy Sarvari
2025-07-18 15:16 ` joseph.maniaci
2025-07-18 15:17 ` joseph.maniaci
2025-07-18 15:40 ` Quentin Schulz
2025-07-17 16:27 ` joseph.maniaci
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=7cc556c6-d347-469a-9ecd-47949e492aed@gmail.com \
--to=skandigraun@gmail.com \
--cc=joseph.maniaci@seagate.com \
--cc=quentin.schulz@cherry.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.