From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/4] base.bbclass: Add compatibility package name mapping handler
Date: Wed, 27 Jul 2011 09:44:26 -0500 [thread overview]
Message-ID: <4E30244A.5030209@windriver.com> (raw)
In-Reply-To: <7cdd5b62608ae2047d4fdd2ee98e452398401b1e.1311776363.git.richard.purdie@linuxfoundation.org>
On 7/27/11 9:29 AM, Richard Purdie wrote:
> This means if PKGARCHCOMPAT_ARMV7A is set, "armv7a-vfp-neon" is renamed
> to be "armv7a". Other compatibility mappings can be added as needed.
There are multiple armv7 cores without neon... I think there might even be one
or two custom cores w/o VFP. (Yes I know this violates the core spec from ARM,
but people do that all of the time.)
--Mark
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
> ---
> meta/classes/base.bbclass | 8 ++++++++
> 1 files changed, 8 insertions(+), 0 deletions(-)
>
> diff --git a/meta/classes/base.bbclass b/meta/classes/base.bbclass
> index f12b3cb..3ed1bb8 100644
> --- a/meta/classes/base.bbclass
> +++ b/meta/classes/base.bbclass
> @@ -133,6 +133,13 @@ def generate_git_config(e):
> f.write(proxy_command)
> f.close
>
> +def pkgarch_mapping(d):
> + # Compatibility mappings of TUNE_PKGARCH (opt in)
> + if d.getVar("PKGARCHCOMPAT_ARMV7A", True):
> + if d.getVar("TUNE_PKGARCH", True) == "armv7a-vfp-neon":
> + d.setVar("TUNE_PKGARCH", "armv7a")
> +
> +
> addhandler base_eventhandler
> python base_eventhandler() {
> from bb import note, error, data
> @@ -203,6 +210,7 @@ python base_eventhandler() {
>
> if name == "ConfigParsed":
> generate_git_config(e)
> + pkgarch_mapping(e.data)
>
> if not data in e.__dict__:
> return
next prev parent reply other threads:[~2011-07-27 14:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-27 14:29 [PATCH 0/4] Various Misc tweaks Richard Purdie
2011-07-27 14:29 ` [PATCH 1/4] base.bbclass: Add compatibility package name mapping handler Richard Purdie
2011-07-27 14:44 ` Mark Hatle [this message]
2011-07-27 14:50 ` Richard Purdie
2011-07-27 15:45 ` Koen Kooi
2011-07-27 15:02 ` Phil Blundell
2011-07-27 15:04 ` Mark Hatle
2011-07-27 15:06 ` Koen Kooi
2011-07-27 15:13 ` Phil Blundell
2011-07-30 18:43 ` Khem Raj
2011-07-30 20:01 ` Phil Blundell
2011-07-27 14:29 ` [PATCH 2/4] gcc: Drop part of the 64bithack patch which is no longer used Richard Purdie
2011-07-28 14:35 ` Lu, Lianhao
2011-07-28 14:55 ` Kumar Gala
2011-08-02 18:28 ` Khem Raj
2011-07-27 14:29 ` [PATCH 3/4] module-init-tools-cross: Drop static binaries patch as a better fix has been merged Richard Purdie
2011-07-27 14:29 ` [PATCH 4/4] base.bbclass: Fix PACKAGE_ARCH typo Richard Purdie
2011-07-30 18:40 ` Khem Raj
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=4E30244A.5030209@windriver.com \
--to=mark.hatle@windriver.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.