From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from aws-us-west-2-korg-lkml-1.web.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.lore.kernel.org (Postfix) with ESMTP id 12C3AC83F1A for ; Fri, 18 Jul 2025 15:16:44 +0000 (UTC) Subject: Re: [yocto] Environmental variable present in do_compile() {}, bitbake recipe -e, but is missing from do_configure() {} #bitbake To: "Gyorgy Sarvari" , yocto@lists.yoctoproject.org From: joseph.maniaci@seagate.com X-Originating-Location: Minnesota, US (134.204.180.68) X-Originating-Platform: Windows Firefox 128 User-Agent: GROUPS.IO Web Poster MIME-Version: 1.0 Date: Fri, 18 Jul 2025 08:16:40 -0700 References: In-Reply-To: Message-ID: <27507.1752851800140508582@lists.yoctoproject.org> Content-Type: multipart/alternative; boundary="O170CBmCiYn6LRF6ugS4" List-Id: X-Webhook-Received: from li982-79.members.linode.com [45.33.32.79] by aws-us-west-2-korg-lkml-1.web.codeaurora.org with HTTPS for ; Fri, 18 Jul 2025 15:16:44 -0000 X-Groupsio-URL: https://lists.yoctoproject.org/g/yocto/message/65682 --O170CBmCiYn6LRF6ugS4 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Fri, Jul 18, 2025 at 01:43 AM, Gyorgy Sarvari wrote: >=20 > It goes through the bitbake parser first, and by the time it is > executed, it becomes 'export ABC=3D"AAAAAAAAAAAAAAAHHHHHHHHHHHHHHH"' - th= e > 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 documentat= ion ( https://docs.yoctoproject.org/bitbake/bitbake-user-manual/bitbake-use= r-manual-ref-variables.html#term-BB_ENV_PASSTHROUGH_ADDITIONS ). Not to men= tion all of the CMAKE gotchas I've come across. --O170CBmCiYn6LRF6ugS4 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
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=3D"AAAAAAAAAAAAAAAHHHHHHHHHHHHHHH"' = - the
original ${ABC} is nowhere to be found, because it's a bitbake v= ariable
(just like SRC_URI, for example), not an env var, it was subst= ituted
with the literal value of ${ABC}. And before executing that exp= ort
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 B= B_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. Not to mention all of the CMAKE g= otchas I've come across.
 
 
--O170CBmCiYn6LRF6ugS4--