From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 1/2] bitbake: main: add 2 environment variables
Date: Wed, 20 Apr 2016 10:31:28 +0300 [thread overview]
Message-ID: <1461137489-14968-1-git-send-email-ed.bartosh@linux.intel.com> (raw)
In-Reply-To: <1461076236-9289-1-git-send-email-ed.bartosh@linux.intel.com>
Bitbake uses set of environment variables to set command line
options, e.g. seeting BBTOKEN variable has the same effect
as using --token command line option.
Added new environment variables BBPRECONF and BBPOSTCONF that
are equivalents of --read and --postread command line options.
They can be used by high level scripts to append or prepend
configuration files to conf/local.conf
[YOCTO #9235]
Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
---
bitbake/lib/bb/main.py | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/bitbake/lib/bb/main.py b/bitbake/lib/bb/main.py
index e302173..08ecdda 100755
--- a/bitbake/lib/bb/main.py
+++ b/bitbake/lib/bb/main.py
@@ -250,6 +250,12 @@ class BitBakeConfigParameters(cookerdata.ConfigParameters):
if "BBEVENTLOG" in os.environ:
options.writeeventlog = os.environ["BBEVENTLOG"]
+ if "BBPRECONF" in os.environ:
+ option.prefile.append(os.environ["BBPRECONF"])
+
+ if "BBPOSTCONF" in os.environ:
+ option.postfile.append(os.environ["BBPOSTCONF"])
+
# fill in proper log name if not supplied
if options.writeeventlog is not None and len(options.writeeventlog) == 0:
import datetime
--
2.1.4
next prev parent reply other threads:[~2016-04-20 9:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 14:30 [PATCH] bitbake: main: add 2 environment variables Ed Bartosh
2016-04-19 19:58 ` Richard Purdie
2016-04-20 6:20 ` Ed Bartosh
2016-04-20 7:31 ` Ed Bartosh [this message]
2016-04-20 7:31 ` [PATCH 2/2] bitbake: main: set defaults from env variables Ed Bartosh
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=1461137489-14968-1-git-send-email-ed.bartosh@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=bitbake-devel@lists.openembedded.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.