From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ross Burton <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/4] Don't build gtk+-native
Date: Tue, 05 Mar 2013 23:49:31 +0000 [thread overview]
Message-ID: <1362527371.11727.50.camel@ted> (raw)
In-Reply-To: <cover.1362401323.git.ross.burton@intel.com>
On Mon, 2013-03-04 at 12:52 +0000, Ross Burton wrote:
> We're building gtk+-native (so the X stack, freetype, fontconfig, etc etc) just
> to run gtk-update-icon-cache on the host when building the rootfs.
>
> This series adds a recipe that builds just that binary from a GTK+ tarball using
> a bit of hackery.
>
> For a benchmark of building sato-icon-theme from nothing (no sstate or tmp):
>
> master takes 13:25 to run 1037 tasks.
> ross/gtk takes 9:26 to run 629 tasks.
>
> So that's a four minute gain and 400 less tasks.
Here, my core-image-sato build from populated DL_DIR time fell by about
2.5 minutes due to this changeset (46:59 to 44:17 mins) so a 5% speedup.
Nice! :)
It would seemingly make around six seconds on "bitbake core-image-sato
-c rootfs" from sstate too (5m25 ish).
Cheers,
Richard
prev parent reply other threads:[~2013-03-06 0:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 12:52 [PATCH 0/4] Don't build gtk+-native Ross Burton
2013-03-04 12:52 ` [PATCH 1/4] gtk-update-icon-cache-native: add Ross Burton
2013-03-05 9:17 ` Richard Purdie
2013-03-04 12:52 ` [PATCH 2/4] default-providers: add default virtual provider for gtk-update-icon-cache Ross Burton
2013-03-04 12:52 ` [PATCH 3/4] gtk+: mark as provider of virtual/gtk-update-icon-cache-native Ross Burton
2013-03-04 12:52 ` [PATCH 4/4] gtk-icon-cache: use virtual/gtk-update-icon-cache-native instead of gtk+-native Ross Burton
2013-03-05 23:49 ` Richard Purdie [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=1362527371.11727.50.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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