From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] Remove dependency on X11 when building for qemu machines
Date: Mon, 14 Nov 2011 18:54:16 +0000 [thread overview]
Message-ID: <cover.1321296476.git.paul.eggleton@linux.intel.com> (raw)
Make some adjustments to qemu-config and items it depends upon to avoid
having a hard depencency on building X11. Note that there is still a
dependency chain that builds X11 for core-image-minimal by default
(udev->glib-2.0->dbus...) however, at least you can now remove x11 from
DISTRO_FEATURES and still be able to build an image for a qemu* machine.
As a side bonus because of the oprofileui-server split qemu-config should
not need to be blacklisted for non-GPLv3 builds anymore.
The following changes since commit f2316ff39670ed99382411e15ac035550360fbdd:
opkg: Ensure we use the uname/gname fields when extracting tarballs (2011-11-14 11:15:36 +0000)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib paule/qemu-x11
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/qemu-x11
Paul Eggleton (4):
oprofileui: split server to separate recipe to avoid X11 dependency
qemu-config: split out anjuta-remote-run
distcc: make distccmon-gnome optional and default to off
qemu-config: update DESCRIPTION and LICENSE
meta/recipes-bsp/qemu-config/qemu-config.bb | 12 +-
.../anjuta-remote-run/anjuta-remote-run.bb | 21 ++
.../anjuta-remote-run/COPYING.GPL | 339 ++++++++++++++++++++
.../anjuta-remote-run}/anjuta-remote-run | 0
meta/recipes-devtools/distcc/distcc_2.18.3.bb | 18 +-
.../oprofile/oprofileui-server_git.bb | 13 +
meta/recipes-kernel/oprofile/oprofileui.inc | 11 +-
meta/recipes-kernel/oprofile/oprofileui_git.bb | 12 +-
8 files changed, 398 insertions(+), 28 deletions(-)
create mode 100644 meta/recipes-devtools/anjuta-remote-run/anjuta-remote-run.bb
create mode 100644 meta/recipes-devtools/anjuta-remote-run/anjuta-remote-run/COPYING.GPL
rename meta/{recipes-bsp/qemu-config/qemu-config => recipes-devtools/anjuta-remote-run/anjuta-remote-run}/anjuta-remote-run (100%)
create mode 100644 meta/recipes-kernel/oprofile/oprofileui-server_git.bb
--
1.7.5.4
next reply other threads:[~2011-11-14 19:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 18:54 Paul Eggleton [this message]
2011-11-14 18:54 ` [PATCH 1/4] oprofileui: split server to separate recipe to avoid X11 dependency Paul Eggleton
2011-11-14 18:54 ` [PATCH 2/4] qemu-config: split out anjuta-remote-run Paul Eggleton
2011-11-14 18:54 ` [PATCH 3/4] distcc: make distccmon-gnome optional and default to off Paul Eggleton
2011-11-14 19:17 ` Koen Kooi
2011-11-14 20:39 ` Richard Purdie
2011-11-14 20:55 ` Koen Kooi
2011-11-14 21:48 ` Richard Purdie
2011-11-15 7:58 ` Koen Kooi
2011-11-15 10:15 ` Richard Purdie
2011-11-15 11:44 ` Paul Eggleton
2011-11-15 12:15 ` Koen Kooi
2011-11-15 13:43 ` Richard Purdie
2011-11-15 13:59 ` Koen Kooi
2011-11-15 14:42 ` Richard Purdie
2011-11-15 14:55 ` Koen Kooi
2011-11-15 15:12 ` Richard Purdie
2011-11-15 15:23 ` Koen Kooi
2011-11-15 15:27 ` Paul Eggleton
2011-11-15 15:24 ` Paul Eggleton
2011-11-15 8:47 ` Paul Menzel
2011-11-15 10:51 ` Richard Purdie
2011-11-14 21:56 ` Paul Eggleton
2011-11-14 18:54 ` [PATCH 4/4] qemu-config: update DESCRIPTION and LICENSE Paul Eggleton
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.1321296476.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.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 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.