All of lore.kernel.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: yocto@lists.yoctoproject.org, joseph.maniaci@seagate.com,
	Gyorgy Sarvari <skandigraun@gmail.com>
Subject: Re: [yocto] Environmental variable present in do_compile() {}, bitbake recipe -e, but is missing from do_configure() {} #bitbake
Date: Fri, 18 Jul 2025 17:40:10 +0200	[thread overview]
Message-ID: <5ad4de8a-77ee-4577-88f1-95434f64c29d@cherry.de> (raw)
In-Reply-To: <27507.1752851800140508582@lists.yoctoproject.org>

Hi Joseph,

On 7/18/25 5:16 PM, joseph.maniaci via lists.yoctoproject.org wrote:
> On Fri, Jul 18, 2025 at 01:43 AM, Gyorgy Sarvari wrote:
> 
>>
>> It goes through the bitbake parser first, and by the time it is
>> executed, it becomes 'export ABC="AAAAAAAAAAAAAAAHHHHHHHHHHHHHHH"' - the
>> original ${ABC} is nowhere to be found, because it's a bitbake variable
>> (just like SRC_URI, for example), not an env var, it was substituted
>> with the literal value of ${ABC}. And before executing that export
>> statement, the ABC env var doesn't exist in the build environment at all.
> 
> Man, considering the quantity of search results telling users to use BB_ENV_PASSTHROUGH_ADDITIONS to accomplish what I'm doing, that really feels like something that should be highlighted in red, and bolded, in the documentation ( https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-user-manual-ref-variables.html#term-BB_ENV_PASSTHROUGH_ADDITIONS ). Not to mention all of the CMAKE gotchas I've come across.
> 

Don't hesitate to send patches for the docs :)

The more time one spends working with BitBake the more difficult it is 
to write documentation with the "beginner" eye, so this kind of feedback 
and contribution is very much welcome!

Cheers,
Quentin


  parent reply	other threads:[~2025-07-18 15:40 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
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 [this message]
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=5ad4de8a-77ee-4577-88f1-95434f64c29d@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=joseph.maniaci@seagate.com \
    --cc=skandigraun@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 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.