The required version of BitBake is changing rapidly. At the time of writing (end 2007) BitBake 1.8.latest was required. A safe method is to get the BitBake from a stable Subversion branch (those with an even minor number). svn co http://svn.berlios.de/svnroot/repos/bitbake/branches/bitbake-1.8 ... A bitbake-1.8/classes/base.bbclass U bitbake-1.8 At revision 827. BitBake is checked out now; this completes the first and most critical dependency of OpenEmbedded. Issuing svn up in the bitbake-1.8 directory will update BitBake to the latest stable version, but generally it is a good idea to stick with a specific known working version of BitBake until OpenEmbedded asks you to upgrade.

The OpenEmbedded metadata has a high rate of development, so it's a good idea to stay up to date. You'll need monotone 0.28 to get the metadata and stay up to date. Monotone is available in most distributions and has binaries at Monotone homepage. Next step is getting snapshot of database. wget http://openembedded.org/snapshots/OE.mtn.bz2 http://openembedded.org/snapshots/OE.mtn.bz2.md5 Or if you have monotone 0.30 or later: wget http://www.openembedded.org/snapshots/OE-this-is-for-mtn-0.30.mtn.bz2 wget http://www.openembedded.org/snapshots/OE-this-is-for-mtn-0.30.mtn.bz2.md5 Then verify integrity of snapshot by checking md5sum. md5sum -c OE.mtn.bz2.md5sum Then unpack database. bunzip OE.mtn.bz2 Finally checkout the development branch. mtn --db=OE.mtn co -b org.openembedded.dev

This section is a stub, help us by expanding it

Once BitBake and OpenEmbedded are set up and configured, one can build software and images like this: bitbake <recipe_name> This section is a stub, help us by expanding it