All of lore.kernel.org
 help / color / mirror / Atom feed
From: joseph.maniaci@seagate.com
To: "Alexander Kanavin" <alex.kanavin@gmail.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 09:27:04 -0700	[thread overview]
Message-ID: <16966.1752769624549320472@lists.yoctoproject.org> (raw)
In-Reply-To: <CANNYZj-153HOf3oC_=8PYLwtDYqBQQFNE=hP+JYXikw3YDa7Rg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 577 bytes --]

So in experimenting, I learned that if I did a 'export ABC=3' 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=3'. I can, in the do_configure() step, execute 'export > do_configure.out', examine the file and see that it isn't there.

[-- Attachment #2: Type: text/html, Size: 622 bytes --]

      parent reply	other threads:[~2025-07-17 16:27 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
2025-07-17 16:27   ` joseph.maniaci [this message]

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=16966.1752769624549320472@lists.yoctoproject.org \
    --to=joseph.maniaci@seagate.com \
    --cc=alex.kanavin@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.