Re: proposal to move cogl, clutter and related recipes from oe-core to dedicated meta-clutter layer

[Tomas Frydrych <tf+lists.yocto@r-finger.com>]

Hi Mark,

On 10/05/13 21:37, Mark Hatle wrote:
> One of the key pieces of the oe-core, it must be able to work without
> any additional layers.  It also much be able to be tested without any
> additional layers.
> 
> I personally don't have a preference for the clutter and related items
> on where they live... but I do want to make sure that oe-core can
> standalone as a starting point for people to develop devices.  Part of
> being standalone means that it is capable of being tested.

Yes, but the clutter packages are not being tested, and more to the
point, they cannot be meaningfully tested using oe-core, because such
testing has to be done against a real OGL/GLES implementation -- Clutter
can only be tested properly in conjunction with BSP layer(s). All you
can test with oe-core is the mesa software rasterizer, which is just
about the one thing nobody cares about because it is of no practical use.

There are two ways that tested clutter packages are achievable:

a) Generic clutter recipes in oe-core and BSP specific bbappends in the
BSP layers. There are a couple of problems with this: I don't think the
BSP maintainers have time/impetus for maintaining the bbappends and
testing Clutter, and the BSP support might need upgrading the base
package and dependencies (plus Clutter is a fairly high level package to
be part of a BSP anyway, IMO).

b) A dedicated layer that is not subject to the oe-core constraints and
can make reference to external BSP layers.

Tomas

-- 
http://sleepfive.com