From a25074cf7f3383ea3963c4dabb9507af34f2e3df Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 17 Mar 2011 16:41:43 -0600 Subject: documentation/poky-ref-manual/usingpoky.xml: grammar fix and BitBake fix Fixed a grammar problem and then did a search and replace for "bitbake" to replace with "BitBake". Signed-off-by: Scott Rifenbark --- documentation/poky-ref-manual/usingpoky.xml | 32 ++++++++++++++--------------- 1 file changed, 16 insertions(+), 16 deletions(-) (limited to 'documentation/poky-ref-manual') diff --git a/documentation/poky-ref-manual/usingpoky.xml b/documentation/poky-ref-manual/usingpoky.xml index 79e9dfbf9..2d2e3f6ea 100644 --- a/documentation/poky-ref-manual/usingpoky.xml +++ b/documentation/poky-ref-manual/usingpoky.xml @@ -5,7 +5,7 @@ This section gives an overview of the components that make up Poky - following by information about running poky builds and dealing with any + followed by information about running poky builds and dealing with any problems that may arise. @@ -13,8 +13,8 @@ Poky Overview - The bitbake task executor together with various types of configuration files form the core of Poky. - This section overviews the bitbake task executor and the + The BitBake task executor together with various types of configuration files form the core of Poky. + This section overviews the BitBake task executor and the configuration files by describing what they are used for and they they interact. @@ -48,12 +48,12 @@ Bitbake is the tool at the heart of Poky and is responsible for parsing the metadata, generating a list of tasks from it - and then executing them. To see a list of the options bitbake + and then executing them. To see a list of the options BitBake supports look at 'bitbake --help'. - The most common usage for bitbake is bitbake <packagename>, where + The most common usage for BitBake is bitbake <packagename>, where packagename is the name of the package you want to build (referred to as the 'target' in this manual). The target often equates to the first part of a .bb filename. @@ -64,13 +64,13 @@ Several different versions of matchbox-desktop might exist. Bitbake chooses the one selected by the distribution configuration. - You can get more details about how bitbake chooses between different versions + You can get more details about how BitBake chooses between different versions and providers in the 'Preferences and Providers' section. Bitbake also tries to execute any dependent tasks first. - So for example, before building matchbox-desktop bitbake + So for example, before building matchbox-desktop BitBake would build a cross compiler and glibc if they had not already been built. @@ -197,7 +197,7 @@ The log file for shell tasks is available in ${WORKDIR}/temp/log.do_taskname.pid. For example, the "compile" task of busybox 1.01 on the ARM spitz machine might be tmp/work/armv5te-poky-linux-gnueabi/busybox-1.01/temp/log.do_compile.1234. - To see what bitbake runs to generate that log, look at the corresponding + To see what BitBake runs to generate that log, look at the corresponding run.do_taskname.pid file located in the same directory. @@ -214,10 +214,10 @@ In most cases the series is: fetch, unpack, patch, configure, compile, install, package, package_write and build. The default task is "build" and any tasks on which it depends build first - hence, - the standard bitbake behaviour. + the standard BitBake behaviour. Some tasks exist, such as devshell, that are not part of the default build chain. If you wish to run a task that is not part of the default build chain you can use the - "-c" option in bitbake as follows: + "-c" option in BitBake as follows: $ bitbake matchbox-desktop -c devshell @@ -259,7 +259,7 @@ Dependency Graphs - Sometimes it can be hard to see why bitbake wants to build some other packages before a given + Sometimes it can be hard to see why BitBake wants to build some other packages before a given package you've specified. The bitbake -g targetname command creates the depends.dot and task-depends.dot files in the current directory. @@ -273,8 +273,8 @@ General Bitbake Problems - You can see debug output from bitbake by using the "-D" option. - The debug output gives more information about what bitbake + You can see debug output from BitBake by using the "-D" option. + The debug output gives more information about what BitBake is doing and the reason behind it. Each "-D" option you use increases the logging level. The most common usage is -DDD. @@ -282,9 +282,9 @@ The output from bitbake -DDD -v targetname can reveal why - bitbake chose a certain version of a package or why bitbake + BitBake chose a certain version of a package or why BitBake picked a certain provider. - This command could also help you in a situation where you think bitbake did something + This command could also help you in a situation where you think BitBake did something unexpected. @@ -296,7 +296,7 @@ the command form bitbake -b somepath/somefile.bb. This command form does not check for dependencies so you should use it only when you know its dependencies already exist. - You can also specify fragments of the filename and bitbake checks for a unique match. + You can also specify fragments of the filename and BitBake checks for a unique match. -- cgit v1.2.3