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 AA002C83F34 for ; Thu, 17 Jul 2025 16:27:09 +0000 (UTC) Subject: Re: [yocto] Environmental variable present in do_compile() {}, bitbake recipe -e, but is missing from do_configure() {} #bitbake To: "Alexander Kanavin" , 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: Thu, 17 Jul 2025 09:27:04 -0700 References: In-Reply-To: Message-ID: <16966.1752769624549320472@lists.yoctoproject.org> Content-Type: multipart/alternative; boundary="M4cVm55VaRt4eAeGrMpB" 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 ; Thu, 17 Jul 2025 16:27:09 -0000 X-Groupsio-URL: https://lists.yoctoproject.org/g/yocto/message/65674 --M4cVm55VaRt4eAeGrMpB Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable So in experimenting, I learned that if I did a 'export ABC=3D3' in my envir= onment followed by a 'bitbake whatever', the ABC environment variable would= persist all the way to the do_compile(). However, what I found weird is th= at it is not present in the do_configure() step. To confirm it was present, period, I can see it in 'bitbake whatever -e'. I= can, in the do_compile() step, execute 'export > do_compile.out', examine = the file and see 'export ABC=3D3'. I can, in the do_configure() step, execu= te 'export > do_configure.out', examine the file and see that it isn't ther= e. --M4cVm55VaRt4eAeGrMpB Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
So in experimenting, I learned that if I did a 'export ABC=3D3' in my = environment followed by a 'bitbake whatever', the ABC environment variable = would persist all the way to the do_compile(). However, what I found weird = is that it is not present in the do_configure() step.
 
To confirm it was present, period, I can see it in 'bitbake whatever -= e'. I can, in the do_compile() step, execute 'export > do_compile.out', = examine the file and see 'export ABC=3D3'. I can, in the do_configure() ste= p, execute 'export > do_configure.out', examine the file and see that it= isn't there.
--M4cVm55VaRt4eAeGrMpB--