OpenMoko2007.2

From Openmoko

Revision as of 15:52, 1 August 2007 by Thebohemian (Talk | contribs)

Jump to: navigation, search

As of 2007-07-26 the development of the next version of the OpenMoko distribution has begun.

Goals of the new version are an improved set of PIM applications, improved theming that fixes a lot of the usability problems of the 1st generation design, more formalized UI guidelines and a number of changes in the build system. The latter should introduce more recent software by staying closer in sync with upstream org.openembedded.dev.

An official announcement is expected soon.

(Initially this was named OM-2008 in SVN but renamed shortly after that.)

How to build

Please note that this is no official guide on how to build OM-2007.2 . I am just making my first steps getting this to compile and think it would be a waste of time of I keep problems I found for my own. Additionally it would be good if the new distro gets more exposure and testing so less things will break after the official announcement.

Follow the getting started steps of OpenEmbedded. Use Bitbake from the stable branch from SVN (not the 1.8.6 release - does not work!).

Put the following in your local.conf 

BBFILES = "${HOME}/oe/org.openembedded.dev/packages/*/*.bb"

MACHINE = "fic-gta01"
DISTRO = "openmoko"

The new stuff is the definition of BBFILES. Without that it won't work at all.

Run bitbake <package name> (e.g. openmoko-devel-image).

Flashing an image to the device is not handled by this guide. Hopefully the MokoMakeFile is soon upgraded to be used for OM-2007.2. Since OpenMoko is not using the overlay any more that makefile should be simpler then. :)

Build issues

You may get something like this while the bitbake recipes are parsed: 

Error validating server certificate for 'https://libw100.svn.sf.net:443':
 - The certificate hostname does not match.
 Certificate information:
  - Hostname: *.svn.sourceforge.net
  - Valid: from Fri, 27 Oct 2006 12:05:58 GMT until Sun, 28 Oct 2007 13:05:58 GMT
  - Issuer: Equifax Secure Certificate Authority, Equifax, US
  - Fingerprint: f2:6c:fe:bb:82:92:30:09:72:dd:1c:b3:e7:56:69:c7:7a:df:67:3e

That is an issue in a bitbake file. One should not use the short-name for sourceforge (sf.net) when certificates are only for exact host names. Accept the certificate and everything is fine for now.

Retrieved from "http://wiki.openmoko.org/index.php?title=OpenMoko2007.2&oldid=15666"
Personal tools

As of 2007-07-26 the development of the next version of the OpenMoko distribution has begun.

Goals of the new version are an improved set of PIM applications, improved theming that fixes a lot of the usability problems of the 1st generation design, more formalized UI guidelines and a number of changes in the build system. The latter should introduce more recent software by staying closer in sync with upstream org.openembedded.dev.

An official announcement is expected soon.

(Initially this was named OM-2008 in SVN but renamed shortly after that.)

How to build

Please note that this is no official guide on how to build OM-2007.2 . I am just making my first steps getting this to compile and think it would be a waste of time of I keep problems I found for my own. Additionally it would be good if the new distro gets more exposure and testing so less things will break after the official announcement.

Follow the getting started steps of OpenEmbedded. Use Bitbake from the stable branch from SVN (not the 1.8.6 release - does not work!).

Put the following in your local.conf 

BBFILES = "${HOME}/oe/org.openembedded.dev/packages/*/*.bb"

MACHINE = "fic-gta01"
DISTRO = "openmoko"

The new stuff is the definition of BBFILES. Without that it won't work at all.

Run bitbake <package name> (e.g. openmoko-devel-image).

Flashing an image to the device is not handled by this guide. Hopefully the MokoMakeFile is soon upgraded to be used for OM-2007.2. Since OpenMoko is not using the overlay any more that makefile should be simpler then. :)

Build issues

You may get something like this while the bitbake recipes are parsed: 

Error validating server certificate for 'https://libw100.svn.sf.net:443':
 - The certificate hostname does not match.
 Certificate information:
  - Hostname: *.svn.sourceforge.net
  - Valid: from Fri, 27 Oct 2006 12:05:58 GMT until Sun, 28 Oct 2007 13:05:58 GMT
  - Issuer: Equifax Secure Certificate Authority, Equifax, US
  - Fingerprint: f2:6c:fe:bb:82:92:30:09:72:dd:1c:b3:e7:56:69:c7:7a:df:67:3e

That is an issue in a bitbake file. One should not use the short-name for sourceforge (sf.net) when certificates are only for exact host names. Accept the certificate and everything is fine for now.