From: joseph.maniaci@seagate.com
To: joseph.maniaci@seagate.com, yocto@lists.yoctoproject.org
Subject: Re: [yocto] Environmental variable present in do_compile() {}, bitbake recipe -e, but is missing from do_configure() {} #bitbake
Date: Thu, 17 Jul 2025 11:16:40 -0700 [thread overview]
Message-ID: <29250.1752776200152802991@lists.yoctoproject.org> (raw)
In-Reply-To: <27507.1752773309289469706@lists.yoctoproject.org>
[-- Attachment #1: Type: text/plain, Size: 1082 bytes --]
Okay, maybe one more question for the next poor soul that has the same-ish issue
Why does this work:
*** Prior to bitbake ***
export ABC="AAAAAAAAAAAAAAAHHHHHHHHHHHHHHH"
export BB_ENV_PASSTHROUGH_ADDITIONS="$BB_ENV_PASSTHROUGH_ADDITIONS ABC"
*** bitbake recipe ***
....
do_configure () {
export ABC=${ABC} && cmake_do_configure } <<<--- Obviously referencing and seeing ${ABC}
....
CMAKE configures and compiles successfully
but this doesn't
*** bitbake recipe ***
....
do_configure () {
cmake_do_configure <<<--- ${ABC} doesn't make it to cmake
}
....
*** cmakelists.txt ***
if ( NOT DEFINED ENV{ABC})
message (FATAL_ERROR "Undefined environmental variable: ABC \n " )
endif ()
*** bitbake output ***
....
| DEBUG: Executing shell function do_configure
....
*** cmake output ***
| CMake Error at CMakeLists.txt:12 (message):
| Undefined environmental variable: ABC
Even doing something like the following makes it visible to CMAKE
SOME_VAR = "${ABC}"
do_configure () {
export ABC=${SOME_VAR} && cmake_do_configure
}
[-- Attachment #2: Type: text/html, Size: 2860 bytes --]
next prev parent reply other threads:[~2025-07-17 18:16 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
2025-07-17 17:28 ` joseph.maniaci
2025-07-17 18:16 ` joseph.maniaci [this message]
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=29250.1752776200152802991@lists.yoctoproject.org \
--to=joseph.maniaci@seagate.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 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.