From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from vms173009pub.verizon.net ([206.46.173.9]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1Q99W2-0006vy-GN for openembedded-core@lists.openembedded.org; Mon, 11 Apr 2011 07:18:23 +0200 Received: from gandalf.denix.org ([unknown] [108.18.140.4]) by vms173009.mailsrvcs.net (Sun Java(tm) System Messaging Server 7u2-7.02 32bit (built Apr 16 2009)) with ESMTPA id <0LJH005EF2MHMAT2@vms173009.mailsrvcs.net> for openembedded-core@lists.openembedded.org; Mon, 11 Apr 2011 00:15:59 -0500 (CDT) Received: by gandalf.denix.org (Postfix, from userid 1000) id 9A8CD14AF5B; Mon, 11 Apr 2011 01:15:53 -0400 (EDT) Date: Mon, 11 Apr 2011 01:15:53 -0400 From: Denys Dmytriyenko To: Patches and discussions about the oe-core layer Message-id: <20110411051553.GA7131@denix.org> References: <52BC8856-1494-4AC6-B04F-0A9DC5A8AB2B@dominion.thruhere.net> <1302088073.2355.3.camel@scimitar> <20110410015223.GA672@denix.org> <4171961B-5671-4411-80AB-11A99D364310@dominion.thruhere.net> MIME-version: 1.0 In-reply-to: <4171961B-5671-4411-80AB-11A99D364310@dominion.thruhere.net> User-Agent: Mutt/1.5.16 (2007-06-09) Subject: Re: [PATCH 0/1] Clutter-1.6 fix X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Apr 2011 05:18:24 -0000 Content-type: text/plain; charset=us-ascii Content-disposition: inline On Sun, Apr 10, 2011 at 08:12:45AM -0700, Koen Kooi wrote: > > > Op 9 apr. 2011 om 18:52 heeft Denys Dmytriyenko het volgende geschreven: > > > On Wed, Apr 06, 2011 at 12:07:52PM +0100, Joshua Lock wrote: > >> 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 > >>>> > >>>> 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. > > > > FWIW, it would be very nice to bring SOC_FAMILY feature from OE to oe-core, as > > it's being heavily used in many TI recipes, not just omap3... > > It is already in :) Ah, I see now. Your original post made it sound like it was still OE-only feature not available in oe-core... :) > fwiw, atmel is using it as well for at91 -- Denys