[maemo-developers] [maemo-developers] Building Maemo from scratch

[From: Russell Geldmacher]

Hi Devesh,

For now I was starting with the OpenEmbedded build of Maemo, even
though it seems like only Maemo 1.0 is available in OE. It seems to me
that OE automates exactly what is needed to create a Maemo rootstrap.
Once that rootstrap is created, porting the necessary pacakges to a
new device should be straightforward: you modify the build under the
OE working directory, create a new ipkg and a patch, and apply those
changes to your recipe.

Which brings me to two questions:

1. Is Maemo going to be maintained in OE?
2. I've been working a little from the Maemo/OE document available at:
http://downloads.kernelconcepts.de/maemo-oe.txt -- is the author of
that document on this list, and available for me to ask some questions
to?

Thanks,
rusty

On 1/12/06, Devesh Kothari <devesh.kothari at nokia.com> wrote:
> ext Florian Boor wrote:
>
> >Helo,
> >
> >Russell Geldmacher wrote:
> >
> >
> >
> >>So, as I'd assume, there are package-specific patches for Maemo? These
> >>apply to the pristine tarballs I'm guessing? Where can one get these
> >>patches? (Is that a dumb question showing I know nothing about OE?)
> >>
> >>
> >
> >well... you have two sorts of patches:
> >The maemo source packages are Debian-style sources which sometimes contain
> >patches to be applied before building the source. In addition you sometimes need
> >patches to apply additional fixes to build the sources with OE. These patches
> >are managed in OE, but so far OE doesn't have a mechanism to handle the patches
> >included in the source package. Of course you can extract these patches and add
> >them to OE manually, but it makes maintainance of it much more complicated.
> >
> >
> >Greetings
> >
> >Florian
> >
> >
> >
> Wouldnt it be just easier to do it the debian way inside SB.
>
> 1. get the list of packages right so the dependencies are met.
> 2. If you need to modify or add some components then have them available
> in a different local repo [building, packaging and resolving their
> dependencies is a step that should be done seperately, possibly in
> another SB maemo rootstrap]
> 3. for nokia 770 add the magic packages from nokia binary distribution
>
> and you have your new rootfs for nokia 770.
>
> For other devices, to use maemo, you would have to provide device
> specific stuff. Or even better to get the reverse dependencies on what
> packages depend on packages provided by nokia, and approximate what in
> functionality they would mean for the different device, and have
> packages (dummy or providing similar functionality but for your device
> like device state management, battery management, input methods and VKB etc)
>
> Then comes the desktop part etc, which is hildon, remove all af-desktop
> related components from your build as hildon is  quite n770 800x480
> resolution tied. See what could be used from e.g GPE etc package them as
> debian [that could be quite a work]
>
> Also lot of device startup procedure would have to be streamlined
>
> would be quite lot of work but IMHO doable :) Just IN MY PERSONAL
> OPINION, it would great to see option of 2 toolkits (GPE , Hildon), a
> core base maemo platform + adaptation layers , and device specific
> layer, and common set of development tools and environment [SB etc, with
> different toolkits etc]
>
> Devesh
>
>
>
>
>