[maemo-developers] Ideas for Diablo and Elephanta: OpenEmbedded

From: quim.gil at nokia.com quim.gil at nokia.com
Date: Tue Sep 25 08:35:54 EEST 2007
Mamona will be more useful and successful if it serves properly maemo
developers like Sebastian. I'm sure the INdT guys have this in mind.  :)

In terms of roadmapping for us 

maemo + OE = mamona

INdT is doing pretty well with the development and I don't see a need
for us now to take part directly. Nor have we currently plans of
supporting officially mamona. 

In the meantime we have an official SDK based on Scratchbox, and we
prefer to concentrate energies in improving it. We are relatively happy
about it: it works and we use it ourselves. There are some things we
dislike and as for today we think that we can address them through
something like Scratchbox2 + System QEMU + Raemo + IDE plugins.

"One development for many targets" is an important principle for us, not
always easy to apply. Usage of common components, versions and developer
tools across hardware vendors would help. We try to do the steps to
align as much as possible with the Linux desktop and the diverse mobile
variants based on GNOME/GTK+.

Quim

>No. When I understand mamona right, it is an approach to 
>create a completely free distribution for the N800 (as 
>replacement of maemo).
>The package selection seems to be based on Angstroem and it 
>uses an upstream gcc4.1 with binutils2.17.50.0.5, at the moment [0].
>
>While mamona is a very nice thing, it does not help to produce 
>packages for maemo. For this we would need at least a binary 
>compatible gnu toolchain in OE (mainly gcc, binutils, glibc). 
>Of course, it would be nice to have the hildon libraries 
>buildable there, too. Whereby the later one should be easy, I 
>can't estimate the effort for the toolchain.

More information about the maemo-developers mailing list