Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Ross Burton <ross.burton@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] Don't build gtk+-native
Date: Mon,  4 Mar 2013 12:52:43 +0000	[thread overview]
Message-ID: <cover.1362401323.git.ross.burton@intel.com> (raw)

Hi,

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.

Ross

The following changes since commit 226c4384643da635fb668cdf0ccd32fea943875d:

  btrfs-tools: added PV to git package recipe (2013-03-04 10:04:27 +0000)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib ross/gtk

for you to fetch changes up to 1c10f4983ce9470f80083d3f943a095df6bbc9bb:

  gtk-icon-cache: use virtual/gtk-update-icon-cache-native instead of gtk+-native (2013-03-04 12:39:19 +0000)

----------------------------------------------------------------
Ross Burton (4):
      gtk-update-icon-cache-native: add
      default-providers: add default virtual provider for gtk-update-icon-cache
      gtk+: mark as provider of virtual/gtk-update-icon-cache-native
      gtk-icon-cache: use virtual/gtk-update-icon-cache-native instead of gtk+-native

 meta/classes/gtk-icon-cache.bbclass                |    2 +-
 meta/conf/distro/include/default-providers.inc     |    1 +
 meta/recipes-gnome/gtk+/gtk+.inc                   |    2 +
 .../gtk+/gtk-update-icon-cache-native_3.4.4.bb     |   44 ++++++++++++++++++++
 4 files changed, 48 insertions(+), 1 deletion(-)
 create mode 100644 meta/recipes-gnome/gtk+/gtk-update-icon-cache-native_3.4.4.bb

Ross Burton (4):
  gtk-update-icon-cache-native: add
  default-providers: add default virtual provider for
    gtk-update-icon-cache
  gtk+: mark as provider of virtual/gtk-update-icon-cache-native
  gtk-icon-cache: use virtual/gtk-update-icon-cache-native instead of
    gtk+-native

 meta/classes/gtk-icon-cache.bbclass                |    2 +-
 meta/conf/distro/include/default-providers.inc     |    1 +
 meta/recipes-gnome/gtk+/gtk+.inc                   |    2 +
 .../gtk+/gtk-update-icon-cache-native_3.4.4.bb     |   44 ++++++++++++++++++++
 4 files changed, 48 insertions(+), 1 deletion(-)
 create mode 100644 meta/recipes-gnome/gtk+/gtk-update-icon-cache-native_3.4.4.bb

-- 
1.7.10.4




             reply	other threads:[~2013-03-04 13:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-04 12:52 Ross Burton [this message]
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 ` [PATCH 0/4] Don't build gtk+-native Richard Purdie

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.1362401323.git.ross.burton@intel.com \
    --to=ross.burton@intel.com \
    --cc=openembedded-core@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