From: Ross Burton <ross.burton@intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/3] Depexp fixes
Date: Mon, 5 Aug 2013 17:12:20 +0100 [thread overview]
Message-ID: <cover.1375718812.git.ross.burton@intel.com> (raw)
Hi,
I was doing some depexp runs against a world build and almost died of boredom.
So, after at least five years I'll try and finish depexp off...
Attached is a series to fix a runtime exception and DOUBLE the speed of loading
the data. Whilst this sounds good the time to get the data from the bitbake
structures to the GTK+ widgetry is still ~30 seconds on my machine. Still,
better than 60 seconds.
Ross
The following changes since commit 4cff3defb545643132b7233fcffb3fedc1bf182b:
grep: Add patch for texinfo 5.1 (2013-08-03 10:33:14 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib ross/depexp
for you to fetch changes up to 8b1a3c7eb0110cbb2345d32f26d37cb7fc5e8d6e:
depexp: fix typo in variable name (2013-08-05 16:39:47 +0100)
----------------------------------------------------------------
Ross Burton (3):
depexp: make parse() a member function
depexp: insert data instead of append/set, for speed
depexp: fix typo in variable name
bitbake/lib/bb/ui/depexp.py | 28 +++++++++++-----------------
1 file changed, 11 insertions(+), 17 deletions(-)
Ross Burton (3):
depexp: make parse() a member function
depexp: insert data instead of append/set, for speed
depexp: fix typo in variable name
bitbake/lib/bb/ui/depexp.py | 28 +++++++++++-----------------
1 file changed, 11 insertions(+), 17 deletions(-)
--
1.7.10.4
next reply other threads:[~2013-08-05 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 16:12 Ross Burton [this message]
2013-08-05 16:12 ` [PATCH 1/3] depexp: make parse() a member function Ross Burton
2013-08-05 16:12 ` [PATCH 2/3] depexp: insert data instead of append/set, for speed Ross Burton
2013-08-05 16:12 ` [PATCH 3/3] depexp: fix typo in variable name Ross Burton
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.1375718812.git.ross.burton@intel.com \
--to=ross.burton@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.