From 10b785cbae1b84736810777e0783a62dd0d9f7f5 Mon Sep 17 00:00:00 2001 From: Holger Freyther Date: Sat, 13 May 2006 20:54:26 +0000 Subject: usermanual: use BitBake not bitbake, Bitbake, BitNake, Nakebake... use and whatever they result in --- usermanual/usermanual.xml | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) (limited to 'usermanual/usermanual.xml') diff --git a/usermanual/usermanual.xml b/usermanual/usermanual.xml index 34417379dc..24676eb0c6 100644 --- a/usermanual/usermanual.xml +++ b/usermanual/usermanual.xml @@ -30,8 +30,8 @@ Introduction
Overview - OpenEmbedded is a set of metadata used to crosscompile, package and install software packages. OpenEmbedded is being used to build and maintain a number of embedded Linux distributions, including OpenZaurus, Familiar and SlugOS. - The primary usecase of OpenEmbedded are: + OpenEmbedded is a set of metadata used to crosscompile, package and install software packages. OpenEmbedded is being used to build and maintain a number of embedded Linux distributions, including OpenZaurus, Familiar and SlugOS. + The primary usecase of OpenEmbedded are: Handle crosscompilation. Handle interpackage dependencies @@ -41,7 +41,7 @@ Writing of metadata must be easy and reusable - Together with BitBake, OpenEmbedded satisfies all these and many more. Flexibility and power have always been the priorities. + Together with BitBake, OpenEmbedded satisfies all these and many more. Flexibility and power have always been the priorities.
@@ -52,7 +52,7 @@ At this time the project had pushed buildroot to its limits ipk packages, feeds and images and had support for more than one machine. But it was impossible to use different patches, files for different architectures, machines or distributions. To overcome this shortcoming OpenEmbedded was created. - After a few months other projects started using OpenEmbedded and contributing back. On 7 December 2004 Chris Larson split the project into two parts: Bitbake, a generic task executor and OpenEmbedded, the metadata for bitbake. + After a few months other projects started using OpenEmbedded and contributing back. On 7 December 2004 Chris Larson split the project into two parts: BitBake, a generic task executor and OpenEmbedded, the metadata for BitBake. @@ -61,23 +61,23 @@ OpenEmbedded was created. Metadata
File Layout - OpenEmbedded has three directories holding BitBake metadata conf, + OpenEmbedded has three directories holding BitBake metadata conf, classes and packaes. FIXME
Syntax OpenEmbedded has files ending with .conf, .inc, .bb and.bbclass. The syntax and semantic of these files are best -described in the BitBake manual. +described in the BitBake manual.
Classes - OpenEmbedded provides special BitBake classes to ease compiling, packaging and other things. FIXME. + OpenEmbedded provides special BitBake classes to ease compiling, packaging and other things. FIXME.
Writing Meta Data (Adding packages) -This page will guide you trough the effort of writing a .bb file or recipe in bitbake speak. +This page will guide you trough the effort of writing a .bb file or recipe in BitBake speak. Let's start with the easy stuff, like the package description, license, etc: @@ -111,7 +111,7 @@ SRC_URI = "http://www.host.com/foo/files/${P}.tar.bz2;md5sum=yoursum" -This will tell the fetcher to where to download the sources from and it will check the integrity using md5sum if you provided the appropriate yoursum. You can make one by doing md5sum foo-3.2.2.tar.gz and replacing yoursum with the md5sum on your screen. A typical md5sum will look like this: a6434b0fc8a54c3dec3d6875bf3be8db Notice the ${P} variable, that one holds the package name, ${PN} in bitbake speak and the package version, ${PV} in bitbake speak. It's a short way of writing ${PN}-${PV}. Using this notation means you can copy the recipe when a new version is released without having to alter the contents. You do need to check if everything is still correct, because new versions mean new bugs. +This will tell the fetcher to where to download the sources from and it will check the integrity using md5sum if you provided the appropriate yoursum. You can make one by doing md5sum foo-3.2.2.tar.gz and replacing yoursum with the md5sum on your screen. A typical md5sum will look like this: a6434b0fc8a54c3dec3d6875bf3be8db Notice the ${P} variable, that one holds the package name, ${PN} in BitBake speak and the package version, ${PV} in BitBake speak. It's a short way of writing ${PN}-${PV}. Using this notation means you can copy the recipe when a new version is released without having to alter the contents. You do need to check if everything is still correct, because new versions mean new bugs. Before we can move to the actual building we need to find out which build system the package is using. If we're lucky, we see a configure file in the build tree this is an indicator that we can inherit autotools if we see a .pro file, it might be qmake, which needs inherit qmake. Virtually all gtk apps use autotools: @@ -127,7 +127,7 @@ Lets start the build: -bitbake foo +bitbake foo @@ -175,7 +175,7 @@ It's important to use += so it will get appended to the sta Getting OpenEmbedded
- Getting BitBake + Getting <application>BitBake</application>
@@ -283,7 +283,7 @@ arm-linux-objdump the buildsystem they use to build their software. This will lead to a variety of issues you can run into. This can be failing tests on configuration because of executing cross compiled binaries or crashes at runtime due wrong sizes of basic types. When utilizing OpenEmbedded you avoid searching for patches at many different places and will be able to get things done more quickly. -OpenEmbedded allows you to chooose from a pool of ready to use software packages, allow creation of images and many more. +OpenEmbedded allows you to chooose from a pool of ready to use software packages, allow creation of images and many more.
-- cgit 1.2.3-korg