From: git@git.openembedded.org
To: bitbake-devel@lists.openembedded.org
Subject: Richard Purdie : cooker.py: Add missing BB_WORKERCONTEXT conditionals
Date: Thu, 5 Jan 2012 13:11:53 +0000 (UTC) [thread overview]
Message-ID: <20120105131153.0FFD610335@opal> (raw)
Module: bitbake.git
Branch: master
Commit: bc954f74620959703a0e921fcac3a6892675fe0d
URL: http://git.openembedded.org/?p=bitbake.git&a=commit;h=bc954f74620959703a0e921fcac3a6892675fe0d
Author: Richard Purdie <richard.purdie@linuxfoundation.org>
Date: Thu Jan 5 13:01:36 2012 +0000
cooker.py: Add missing BB_WORKERCONTEXT conditionals
Its desireable to run be able to execute bitbake tasks directly, only
loading as much of the cooker is as necessary to do this. This use case
can be identified by the BB_WORKERCONTEXT variable. There were a couple
of places cooker code needed to be conditional on this but wasn't. This
brings in the missing conditionals from poky where those code paths
are used more heavily completing the support in master.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
lib/bb/cooker.py | 6 +++++-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/lib/bb/cooker.py b/lib/bb/cooker.py
index 27abca0..15243f2 100644
--- a/lib/bb/cooker.py
+++ b/lib/bb/cooker.py
@@ -170,6 +170,9 @@ class BBCooker:
def loadConfigurationData(self):
self.configuration.data = bb.data.init()
+ if not self.server_registration_cb:
+ self.configuration.data.setVar("BB_WORKERCONTEXT", "1")
+
filtered_keys = bb.utils.approved_variables()
bb.data.inheritFromOS(self.configuration.data, self.savedenv, filtered_keys)
@@ -827,7 +830,8 @@ class BBCooker:
for var in data.getVar('__BBHANDLERS') or []:
bb.event.register(var, data.getVar(var))
- bb.fetch.fetcher_init(data)
+ if data.getVar("BB_WORKERCONTEXT", False) is None:
+ bb.fetch.fetcher_init(data)
bb.codeparser.parser_cache_init(data)
bb.parse.init_parser(data)
bb.event.fire(bb.event.ConfigParsed(), data)
reply other threads:[~2012-01-05 13:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120105131153.0FFD610335@opal \
--to=git@git.openembedded.org \
--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.