From: Dongxiao Xu <dongxiao.xu@intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/8 v2][PULL] Hob: bitbake related changes
Date: Wed, 11 Jan 2012 11:03:19 +0800 [thread overview]
Message-ID: <cover.1326249301.git.dongxiao.xu@intel.com> (raw)
Hi Richard,
This is the second pull request for Hob bitbake related changes.
Please help to reviewand pull.
Changes from v1:
1. Fixed a cache issue.
If we run "source oe-init-env-setup", it will force to add POKY/bitbake/bin/ and POKY/scripts into PATH variable,
which changes the configuration hash value. We handled this situation in the new code.
2. event.py: Change the parameter of PackageInfo events.
We have a new approach to get all the available packages in the build repo,
and here we change the way to pass the information.
3. Remove the binding limitation of --server-only and -B.
Thanks,
Dongxiao
The following changes since commit eac9249b40ae1e3aa21e016010c862664e59a8d4:
Richard Purdie (1):
bitbake: Add BBHandledException exception class
are available in the git repository at:
git://git.pokylinux.org/poky-contrib dxu4/hob-bitbake-changes-v2
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dxu4/hob-bitbake-changes-v2
Dongxiao Xu (7):
cache: Use configuration's hash value to validate cache
command.py: add resolve option for generateTargetsTree API
event.py: Add a new event PackageInfo
bitbake: add -B option to bind with interface
bitbake: Add client socket info for BitBakeServerConnection
command.py: add new command to get the CPU info
runqueue: fire sceneQueueTaskStarted event when a setscene queue
starts
Shane Wang (1):
Bitbake: change for adding progress bar in Hob2.
bin/bitbake | 15 +++++---
bitbake/lib/bb/helper.py | 39 ++++++++++++++++++++
lib/bb/cache.py | 34 +++++++-----------
lib/bb/command.py | 23 +++++++++++-
lib/bb/cooker.py | 74 +++++++++++++++++++++++++++++--------
lib/bb/data_smart.py | 21 +++++++++++
lib/bb/event.py | 91 ++++++++++++++++++++++++++++++++++------------
lib/bb/runqueue.py | 10 +++++
lib/bb/server/xmlrpc.py | 10 +++---
lib/bb/ui/knotty.py | 5 ++-
lib/bb/ui/uievent.py | 7 ++--
11 files changed, 253 insertions(+), 76 deletions(-)
create mode 100644 bitbake/lib/bb/helper.py
next reply other threads:[~2012-01-11 3:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 3:03 Dongxiao Xu [this message]
2012-01-11 3:03 ` [PATCH 1/8] cache: Use configuration's hash value to validate cache Dongxiao Xu
2012-01-11 3:03 ` [PATCH 2/8] command.py: add resolve option for generateTargetsTree API Dongxiao Xu
2012-01-11 3:03 ` [PATCH 3/8] event.py: Add a new event PackageInfo Dongxiao Xu
2012-01-11 3:03 ` [PATCH 4/8] Bitbake: change for adding progress bar in Hob2 Dongxiao Xu
2012-01-11 3:03 ` [PATCH 5/8] bitbake: add -B option to bind with interface Dongxiao Xu
2012-01-11 11:38 ` Richard Purdie
2012-01-11 13:30 ` Xu, Dongxiao
2012-01-11 14:29 ` Richard Purdie
2012-01-11 3:03 ` [PATCH 6/8] bitbake: Add client socket info for BitBakeServerConnection Dongxiao Xu
2012-01-11 3:03 ` [PATCH 7/8] command.py: add new command to get the CPU info Dongxiao Xu
2012-01-11 11:34 ` Richard Purdie
2012-01-11 11:52 ` Wang, Shane
2012-01-11 12:02 ` Wang, Shane
2012-01-11 13:24 ` Richard Purdie
2012-01-11 3:03 ` [PATCH 8/8] runqueue: fire sceneQueueTaskStarted event when a setscene queue starts Dongxiao Xu
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=cover.1326249301.git.dongxiao.xu@intel.com \
--to=dongxiao.xu@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox