From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH 0/1] Possible fix for missing -native support for gtk+-native
Date: Fri, 13 Apr 2012 07:19:02 -0600 [thread overview]
Message-ID: <4F8827C6.2040601@mlbassoc.com> (raw)
In-Reply-To: <cover.1334322354.git.Martin.Jansa@gmail.com>
On 2012-04-13 07:09, Martin Jansa wrote:
> Please note that this patch is old and not tested with current HEAD,
> because I'm using different solution in SHR branches - BBCLASSEXTENDs in oe-core
> recipes instead of small bbappends which makes recipe upgrades harder because of
> inter-layer dependencies, see:
> http://lists.linuxtogo.org/pipermail/openembedded-core/2012-March/019624.html
> from this patchset
> http://lists.linuxtogo.org/pipermail/openembedded-core/2012-March/019619.html
>
> But because fix for PACKAGECONFIG added DEPENDS is now in you can find this patch usefull
> and maybe we'll be allowed to move at least some BBCLASSEXTENDs to oe-core later - after release.
>
> The following changes since commit 118734e096fda6c47172025969f3df4cfb0b33c3:
>
> qte-toolchain: add qwte support (2012-04-13 10:50:40 +0200)
>
> are available in the git repository at:
> git://git.openembedded.org/meta-openembedded-contrib jansa/xorg
> http://cgit.openembedded.org/cgit.cgi/meta-openembedded-contrib/log/?h=jansa/xorg
>
> Martin Jansa (1):
> xorg: add more native BBCLASSEXTENDs for gtk+-native
>
> .../xorg-lib/libxcomposite_0.4.3.bbappend | 1 +
> .../xorg-lib/libxcursor_1.1.12.bbappend | 1 +
> .../xorg-lib/libxdamage_1.1.3.bbappend | 1 +
> .../xorg-lib/libxfixes_5.0.bbappend | 1 +
> .../xorg-lib/libxrandr_1.3.2.bbappend | 1 +
> .../xorg-proto/compositeproto_0.4.2.bbappend | 1 +
> .../xorg-proto/damageproto_1.2.1.bbappend | 1 +
> .../xorg-proto/fixesproto_5.0.bbappend | 1 +
> .../xorg-proto/randrproto_1.3.2.bbappend | 1 +
> 9 files changed, 9 insertions(+), 0 deletions(-)
> create mode 100644 meta-oe/recipes-graphics/xorg-lib/libxcomposite_0.4.3.bbappend
> create mode 100644 meta-oe/recipes-graphics/xorg-lib/libxcursor_1.1.12.bbappend
> create mode 100644 meta-oe/recipes-graphics/xorg-lib/libxdamage_1.1.3.bbappend
> create mode 100644 meta-oe/recipes-graphics/xorg-lib/libxfixes_5.0.bbappend
> create mode 100644 meta-oe/recipes-graphics/xorg-lib/libxrandr_1.3.2.bbappend
> create mode 100644 meta-oe/recipes-graphics/xorg-proto/compositeproto_0.4.2.bbappend
> create mode 100644 meta-oe/recipes-graphics/xorg-proto/damageproto_1.2.1.bbappend
> create mode 100644 meta-oe/recipes-graphics/xorg-proto/fixesproto_5.0.bbappend
> create mode 100644 meta-oe/recipes-graphics/xorg-proto/randrproto_1.3.2.bbappend
Why can't these changes just go in the main recipes? Surely adding
BBCLASSEXTEND = "native"
to a recipe has no effect unless you need to build the -native version?
Note: I too have been carrying such .bbappend files in my own layers for
a long time. It would be good to just admit that sometimes the -native
form is needed and fix the primary recipes.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2012-04-13 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 13:09 [meta-oe][PATCH 0/1] Possible fix for missing -native support for gtk+-native Martin Jansa
2012-04-13 13:09 ` [meta-oe][PATCH 1/1] xorg: add more native BBCLASSEXTENDs " Martin Jansa
2012-04-13 13:19 ` Gary Thomas [this message]
2012-04-13 13:34 ` [meta-oe][PATCH 0/1] Possible fix for missing -native support " Martin Jansa
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=4F8827C6.2040601@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-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.