stuffdirectory. BitBake build tool website and take the latest archive tarball. follow the advice: simply install it in your OEDirectoryTree and make a generic link:
tar xvzf bitbake-1.8.18.tar.gz ln -s bitbake-1.8.18 bitbakeOEDirectoryTree, download a snapshot of the OpenEmbedded database using the GIT Souce Code Management tool.
git clone git://git.openembedded.org/openembedded openembeddedor using HTTP protocol:
git clone http://repo.or.cz/r/openembedded.git openembeddedMake sure to call the directory where you will clone the GIT source
openembedded. This name will be used in the following procedure and in the
site.confconfiguration file. Then create a local branch based on OpenEmbedded
cd openembedded git checkout -b stable_2009_mybranch origin/stable/2009 cd ..For demo root filesystems available in the GettingStarted page, we used the following commit ID :
stable/2009branch should be stable enough to be able to build using those instructions even with a more recent
HEADfor this branch.
|OpenEmbedded database|| Web interface:
|overlay directory tree archive|
wget ftp://ftp.linux4sam.org/pub/oe/linux4sam_x.y/oe_at91sam.tgz tar xvzf oe_at91sam.tgzThis archive contains the configuration files, recipes that will overload the original ones from the OpenEmbedded project. The
oe_env.shscript will allow you to setup local configuration variables needed for your rootfs to build.
oe_at91sam/conf/local.conf. This configuration file will overload the
openembedded/conf/local.confone. Read comments in it as it will bring you valuable information and allow you to adapt it to your own environment and building host (directory structure for example). Choose the proper machine type: we will use
at91sam9m10g45ekfor this setup:
MACHINE ?= "at91sam9m10g45ek"OEDirectoryTree. To start the building, source the
source ./oe_env.shThen begin building the distribution with a little set of packages:
bitbake base-imageeven a minimal image will require a big amount of time because of the cross-toolchain building process. The console and graphical images are built using the following recipes respectively:
bitbake console-at91sam9-image bitbake x11-at91sam9-imageOr for AT91SAM9M10 based boards:
bitbake x11-at91sam9m10-imageThis will allow you to take advantage of video features of this chip. This image will include kernel and Gstreamer components needed to use the hardware video decoder.
bitbake -c listtasks <package_name>You can use one of those tasks to have a fine grained control over the package building. The structure of a BitBake file explained: BitBake Metadata
|gz||oe_angstrom_at91.diff.gz||manage||192.5 K||2008-04-15 - 13:13||UnknownUser||linux4sam_1.2_20080415|
|gz||oe_angstrom_at91-2.diff.gz||manage||194.9 K||2008-12-12 - 12:56||UnknownUser||linux4sam_1.4_20081212|
|gz||oe_angstrom_at91-3.diff.gz||manage||195.9 K||2009-07-23 - 15:17||UnknownUser||linux4sam_1.6_20090723|
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.
ARM® and others are registered trademarks or trademarks of ARM Ltd. Other terms and product names may be trademarks of others.
Ideas, requests, contributions ? Connect to LinksToCommunities page.