From: Phil Blundell <pb@pbcl.net>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: proposal to move cogl, clutter and related recipes from oe-core to dedicated meta-clutter layer
Date: Wed, 15 May 2013 21:49:28 +0100 [thread overview]
Message-ID: <1368650968.16243.145.camel@pb-ThinkPad-R50e> (raw)
In-Reply-To: <CAP9ODKpqFxzooVtRzzfDzOQcicXQYnJ3wp0qO-jHyt1fi+1XGQ@mail.gmail.com>
On Wed, 2013-05-15 at 16:28 -0300, Otavio Salvador wrote:
> I agree but it seems it hadn't succeed in this specific case until
> now. I personally think Clutter will benefit from getting a specific
> place to look at and it does seem multiple people has been adding
> Clutter recipes in their internal layers (Phil for example, Guacamayo
> project and so on).
I did actually have a couple of goes at trying to factor out some of our
local changes to the clutter recipes for submission to oe-core, but on
each occasion I gave up because the effort seemed to outweigh the
benefits.
For what it's worth, some of the ways in which our local recipes diverge
from what's in oe-core are:
- we have a different (newer) version
- we build from a local git checkout, srctree-style, because our sources
are significantly patched compared to upstream
- we use eglnative mostly, though we might start wanting to use glx
under qemu for testing (subject to getting a suitable mesa)
- we have a slightly funky 2-stage bootstrap process for cogl in order
to break the dependency cycle with cairo; this involves hacks to the
recipes for cogl, cairo, pango and harfbuzz (at least) which I suspect
would not be very palatable to oe-core.
The net result of all this is that, whenever I try to factor out a set
of stuff that's "generic clutter" and could go into oe-core, I end up
with recipes that have virtually nothing in common with what we're
actually using and consequently don't actually solve any of my problems.
However, I have no doubt that someone cleverer than me could do a better
job of it.
p.
next prev parent reply other threads:[~2013-05-15 21:08 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-08 15:11 proposal to move cogl, clutter and related recipes from oe-core to dedicated meta-clutter layer Tomas Frydrych
2013-05-08 15:23 ` Phil Blundell
2013-05-08 16:34 ` Tomas Frydrych
2013-05-08 15:23 ` Richard Purdie
2013-05-08 16:20 ` Tomas Frydrych
2013-05-10 9:05 ` Richard Purdie
2013-05-10 10:56 ` Tomas Frydrych
2013-05-10 11:32 ` Richard Purdie
2013-05-10 16:39 ` Tomas Frydrych
2013-05-10 17:19 ` Richard Purdie
2013-05-10 20:22 ` Otavio Salvador
2013-05-10 20:37 ` Mark Hatle
2013-05-10 21:15 ` Otavio Salvador
2013-05-13 9:30 ` Tomas Frydrych
2013-05-13 15:41 ` Phil Blundell
2013-05-13 15:44 ` Burton, Ross
2013-05-14 9:14 ` Tomas Frydrych
2013-05-14 16:55 ` Paul Eggleton
2013-05-15 9:19 ` Tomas Frydrych
2013-05-15 9:49 ` Paul Eggleton
2013-05-15 11:35 ` Tomas Frydrych
2013-05-15 11:53 ` Otavio Salvador
2013-05-15 13:20 ` Andreas Oberritter
2013-05-15 14:09 ` Paul Eggleton
2013-05-15 16:34 ` Tomas Frydrych
2013-05-15 16:54 ` Otavio Salvador
2013-05-15 17:22 ` Paul Eggleton
2013-05-15 17:30 ` Richard Purdie
2013-05-15 17:36 ` Otavio Salvador
2013-05-15 18:24 ` Paul Eggleton
2013-05-15 19:28 ` Otavio Salvador
2013-05-15 20:49 ` Phil Blundell [this message]
2013-05-16 9:01 ` Tomas Frydrych
2013-05-16 10:35 ` Phil Blundell
2013-05-16 11:21 ` Tomas Frydrych
2013-05-16 14:35 ` Phil Blundell
2013-05-17 12:30 ` Paul Eggleton
2013-05-16 9:22 ` Tomas Frydrych
2013-05-15 19:43 ` Richard Purdie
2013-05-16 9:21 ` Tomas Frydrych
2013-05-10 21:07 ` Martin Jansa
2013-05-10 22:18 ` Richard Purdie
2013-05-11 20:39 ` Otavio Salvador
2013-05-11 21:49 ` Richard Purdie
2013-05-14 16:23 ` Philip Balister
2013-05-13 9:31 ` Tomas Frydrych
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=1368650968.16243.145.camel@pb-ThinkPad-R50e \
--to=pb@pbcl.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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