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 Phil,

On 13/05/13 16:41, Phil Blundell wrote:
> It seems a bit hyperbolic to claim that testing clutter is impossible
> without GPU hardware (either real or emulated).  The majority of the
> code even in cogl, and virtually all the code in clutter itself, is
> mostly independent of the underlying GL implementation.  From the point
> of view of testing whether clutter basically "works" and is correctly
> built/packaged it seems as though this ought to be quite sufficient.

There are too separate issues: testing clutter itself, and using clutter
to test other parts of the graphics stack.

Re the former, all you can say after testing cogl/clutter against mesa
software rasterizer is that a particular configuration and a particular
backend (in oe-core that would be the GLX backend) work with mesa
software rasterizer. This says nothing about any other configuration,
with any other backend or whether it works with any other GL/GLES
implementation.

In reality, cogl/clutter need patches to build against the likes of TI's
GLES (e.g., Beagleboard) or to work on the likes of RaspberryPi, and
these patches cannot be included in oe-core, of course, because oe-core
knows nothing of such machines. Then there are little annoyances, like
the fact that over the last year or so, clutter has tended to have a
dependency on a specific but mostly random versions of libxkbcommon
(from what I can gather, determined more then anything by whatever the
Fedora packager happened to package and what version of Fedora the
clutter maintainer was using), or Clutter's customary insistence on as
recent glib as you can get. This can all be nicely encapsulated in small
layer.

Regarding using clutter to test other parts of the graphics stack, which
is what Richard is wanting clutter in oe-core for, this amounts to
testing mesa sw rasterizer. There is limited value here, it's the one GL
implementation that nobody using Yocto to build images will be deploying
for real, so this is a weak argument for needing clutter in oe-core.

Tomas

-- 
http://sleepfive.com