m (Replacing '\[\[Openmoko\]\]' with 'Openmoko')
m (Category changes: -Openmoko, +System Developers)
|Line 26:||Line 26:|
Revision as of 10:53, 7 September 2008
English • العربية • Български • Česky • Dansk • Deutsch • Esperanto • Eesti • Español • فارسی • Suomi • Français • עברית • Magyar • Italiano • 한국어 • Nederlands • Norsk (bokmål) • Polski • Português • Română • Русский • Svenska • Slovenčina • Українська • 中文(中国大陆) • 中文(台灣) • Euskara • Català
Openmoko, our distribution, is built using OpenEmbedded. OpenEmbedded will:
- Generate (cross-compile) software packages for multiple embedded targets.
- Handle different hardware architectures, and support multiple releases across those architectures.
For more information please see the Open Embedded website.
Building the Openmoko distribution with OpenEmbedded
Note that you probably don't want to build Openmoko with OpenEmbedded, if you are an application developer. In that case, you better use our prebuilt Toolchain. Building Openmoko is a time-, cpu- and diskspace-consuming process which should only be done if you are a system integrator and want to customize your Openmoko distribution.
The facility called MokoMakefile simplifies building OpenEmbedded, however it also shields you from a lot of knowledge. In case you are the aformentioned system integrator / distribution customizer, we strongly advise you to use BitBake and OpenEmbedded directly.
The official Openmoko branch of the OpenEmbedded database can be found at Git.Openmoko.Org.
Upstream Source tarballs
When bitbake builds a particular OE package, it downloads the original source code of the upstream project (e.g. Linux kernel) and patches from the internet. After downloading sources, bitbake applies a series of patches to the tree. These patches have either been downloaded from the internet or are contained in the OpenEmbemdded metadata repository. The unpatched source tarballs are available from http://downloads.openmoko.org/sources/
|TODO: finish article (See: To-Do List)|