From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/1] Clutter-1.6 fix
Date: Wed, 06 Apr 2011 12:07:52 +0100 [thread overview]
Message-ID: <1302088073.2355.3.camel@scimitar> (raw)
In-Reply-To: <52BC8856-1494-4AC6-B04F-0A9DC5A8AB2B@dominion.thruhere.net>
On Mon, 2011-04-04 at 15:39 +0200, Koen Kooi wrote:
> Op 4 apr 2011, om 15:31 heeft Joshua Lock het volgende geschreven:
>
> > From: Joshua Lock <josh@linux.intel.com>
> >
> > I found a couple of issues with the Clutter 1.6 recipes I submitted recently
> > which I've addressed in the attached patch.
> >
> > As an aside I've noticed that we have a COMPATIBLE_MACHINE line in
> > clutter.inc, I think we're going to need to find a more suitable mechanism
> > for specifying compatible machines for this recipe set going forwards.
> >
> > Any ideas? Perhaps some MACHINE_FEATURE which must exist for Clutter (and
> > other GL dependent recipes) to build?
>
> What we did in OE .dev was:
>
> 1) introduce SOC_FAMILY to group, well, SOC families (e.g. OMAP3)
> 2) Extend base.bbclass to allow COMPATIBLE_MACHINE = $SOC_FAMILY.
> 3) Add COMPATIBLE_MACHINE = omap3 to the GLES recipes
> 4) DEPENDS_omap3 = libgles-omap3 in clutter.inc
>
> So for machines in the omap3 class it will build libgles-omap3 and not
> for others. So the compatibility is defined at the GL level instead of
> the clutter level.
Thanks for sharing Koen. This sounds like a reasonable approach. I'd be
curious to hear if there are any objections before I try and work up a
patch series.
Regards,
Joshua
--
Joshua Lock
Yocto Build System Monkey
Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-04-06 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 13:31 [PATCH 0/1] Clutter-1.6 fix Joshua Lock
2011-04-04 13:31 ` [PATCH 1/1] clutter-1.6: fix tarball md5sum and add json-glib to dependencies Joshua Lock
2011-04-04 13:39 ` [PATCH 0/1] Clutter-1.6 fix Koen Kooi
2011-04-06 11:07 ` Joshua Lock [this message]
2011-04-10 1:52 ` Denys Dmytriyenko
2011-04-10 15:12 ` Koen Kooi
2011-04-11 5:15 ` Denys Dmytriyenko
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=1302088073.2355.3.camel@scimitar \
--to=josh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox