OpenEmbedded

We are proud to report that our project received the TuxMobil GNU/Linux Award 2005. On behalf of the OE core developer team, I want to thank all people who contributed to OpenEmbedded in one way or the other - you all made this success possible! ... [More] OpenEmbedded just hit the 2600 build files mark - which are used to produce over 6000 packages for your embedded Linux distribution. We are really commited to this project and will surely continue to improve the Linux experience on mobile computers. Michael Lauer (mickeyl) August, 2nd, 2005. [Less]

Due to the changes in the BitKeeper license policies, we now use the Monotone SCM. Monotone is a distributed version control system much like BitKeeper was. Push access to oe-devel.bkbits.net has been revoked today and all developers are requested to ... [More] send monotone keys to both [email protected] and [email protected]. Currently, the following servers are supposed to serve the "org.openembedded.*" branches: monotone.vanille.de (official server) ewi546.ewi.utwente.nl (primary backup) dominion.kabel.utwente.nl (secondary backup, only use if all else fails) Please use the branch org.openembedded.dev for changes. Eventually we will move the primary repository over to openembedded.org. See the MonotonePhraseBook for some details on how to develop OpenEmbedded using Monotone. Note that you now need monotone 0.20 to connect to our servers Note as well that monotone 0.20 expects a wildcard of branches ("org.openembedded.*") instead of a collection (org.openembedded) Michael Lauer (mickeyl) June, 30th, 2005, updated on July, 16th, 2005. [Less]

A new edition of the OOO Newsletter is available, covering the latest news in the BitBake, OpenEmbedded, OpenZaurus, Opie, and GPE projects. Michael Lauer (mickeyl) 2005-05-08

A new edition of the OOO Newsletter is available, covering the latest news in the BitBake, OpenEmbedded, OpenZaurus, Opie, and GPE projects. kergoth 2005-01-06

In order to prepare for the 1.0 release of the OpenEmbedded core library/tools, we've made some serious changes that people need to be aware of. What we used to refer to as the "OE core" has been renamed to "BitBake". The name was chosen due to our ... [More] tasks resembling "recipes" to be followed. We came to this decision because the core itself is not in any way bound to embedded use. Only our metadata (classes, configuration files, and packages) is specific to embedded. We also decided that the core didn't really benefit from the peer to peer nature of BitKeeper, so we moved the core to Subversion over at berliOS. Because our metadata was indeed bound to embedded, it was renamed was well. It is no longer just the "packages", or the "OpenEmbedded metadata". Our metadata is now called "OpenEmbedded". We think that this should make things a bit less confusing for the user. OpenEmbedded is our metadata, and BitBake is the tool that acts on that metadata. OpenEmbedded is to Makefiles as BitBake is to make. A few minor changes were made while we were at it. The old "oebuild" tool is now dead, and "bitbake" (which was formerly "oemake") now accepts a -b or --buildfile commandline argument to act on a specific file instead of parsing everything. The current working directory is no longer automatically in BBPATH, so people now have to be certain that their build directory is in their BBPATH. And finally, the upstream packages directory was renamed to openembedded, and the actual packages were moved to a subdirectory of that named "packages". The GettingStarted page has been updated to account for the changes, and there is a BitBake Users Manual available. kergoth 2004-12-20 [Less]

Welcome to Open Embedded. As you can see, some changes have been made to the site. We will be making changes regularly. Feel free to give suggestions or comments to me via the irc channel or the email list. cterry 2004-10-27