From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: MeeGo support in OE
Date: Mon, 28 Jun 2010 09:23:24 +0100 [thread overview]
Message-ID: <1277713404.29314.3248.camel@rex> (raw)
In-Reply-To: <i0220d$htp$1@dough.gmane.org>
On Fri, 2010-06-25 at 12:56 +0200, Koen Kooi wrote:
> On 25-06-10 09:01, Andreas Mueller wrote:
> > My investigations for a 'colorful' embedded environment lead me to Meego (http://meego.com/).
> >
> > On the webpage we learn that this is a platform independent environment but there are only few platforms supported (Nokia N900 / Beaglebord / few Intel netbooks).
> >
> > To have full platform-independency I would like to have Meego (maybe parts of it only) within OE and started already with easiest part uxlaunch (very tiny dm - see
> > git://gitorious.org/meego-os-base/uxlaunch.git). This is already tested with xfce environment but before posting a patch here I would like to do some further tests with gnome/enlightenment and
> > see what happens in case another dm is found in the image.
> >
> > Next step planned is mutter. Here I would like to use the original gnome sources and check the diffs to meego branch.
> >
> > Now my questions:
> >
> > - Are there any objections including meego parts (licensing / don't like Intel/Nokia..) in OE
> > - Are there already proceedings related to mutter ongoing? Or is there a reason that mutter is not in OE other than nobody has done so far?
>
> I didn't add mutter because at the time it didn't build against
> clutter/gles. It think that has changed now :)
>
> I would very much like to build meego components in OE!
You could do worse than look at meta-moblin in Poky which has recipes
for some components like mutter.
Cheers,
Richard
next prev parent reply other threads:[~2010-06-28 8:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 7:01 MeeGo support in OE Andreas Mueller
2010-06-25 10:56 ` Koen Kooi
2010-06-28 8:23 ` Richard Purdie [this message]
2010-06-28 11:12 ` Andreas Mueller
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=1277713404.29314.3248.camel@rex \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.