From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] base.bbclass: add support for SOC_FAMILY in COMPATIBLE_MACHINES
Date: Tue, 03 Aug 2010 20:19:59 -0400 [thread overview]
Message-ID: <20100804001959.GF17391@denix.org> (raw)
In-Reply-To: <1280872040-31952-1-git-send-email-chase.maupin@ti.com>
On Tue, Aug 03, 2010 at 04:47:20PM -0500, Chase Maupin wrote:
> * Add support for using SOC_FAMILY in the COMPATIBLE_MACHINES
> setting for a recipe.
> * This will allow recipes to work for entire families of
> devices without having to maintain/update the compatible
> devices as new devices are added into a family
>
> Signed-off-by: Chase Maupin <chase.maupin@ti.com>
Acked-by: Denys Dmytriyenko <denys@ti.com>
While SOC_FAMILY feature is relatively new on its own, it was designed and now
being extensively used with TI machines and corresponding recipes as an
effective override - e.g. covering many OMAP3-based machines with a single
VAR_omap3 = "VAL" expression.
> ---
> classes/base.bbclass | 4 +++-
> 1 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/classes/base.bbclass b/classes/base.bbclass
> index 1847491..02c7875 100644
> --- a/classes/base.bbclass
> +++ b/classes/base.bbclass
> @@ -389,7 +389,9 @@ python () {
> import re
> this_machine = bb.data.getVar('MACHINE', d, 1)
> if this_machine and not re.match(need_machine, this_machine):
> - raise bb.parse.SkipPackage("incompatible with machine %s" % this_machine)
> + this_soc_family = bb.data.getVar('SOC_FAMILY', d, 1)
> + if this_soc_family and not re.match(need_machine, this_soc_family):
> + raise bb.parse.SkipPackage("incompatible with machine %s" % this_machine)
>
> need_target = bb.data.getVar('COMPATIBLE_TARGET_SYS', d, 1)
> if need_target:
> --
> 1.7.0.4
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2010-08-04 0:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-03 21:47 [PATCH] base.bbclass: add support for SOC_FAMILY in COMPATIBLE_MACHINES Chase Maupin
2010-08-04 0:19 ` Denys Dmytriyenko [this message]
2010-08-04 5:20 ` Khem Raj
2010-08-04 11:17 ` Michael 'Mickey' Lauer
2010-08-04 11:48 ` Phil Blundell
2010-08-04 14:11 ` Maupin, Chase
2010-08-04 16:50 ` Denys Dmytriyenko
2010-08-04 21:50 ` Phil Blundell
2010-08-04 16:13 ` Denys Dmytriyenko
2010-08-04 16:59 ` Graeme Gregory
2010-08-04 17:21 ` Denys Dmytriyenko
2010-08-04 19:41 ` Graeme Gregory
2010-08-04 9:13 ` Koen Kooi
2010-08-04 9:44 ` Frans Meulenbroeks
2010-08-04 19:02 ` Tom Rini
2010-08-04 9:54 ` Phil Blundell
2010-08-04 19:49 ` Khem Raj
2010-08-04 20:24 ` Maupin, Chase
2010-08-04 21:37 ` Khem Raj
2010-08-04 23:56 ` Koen Kooi
2010-08-05 4:38 ` 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=20100804001959.GF17391@denix.org \
--to=denis@denix.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox