From 296bb748f694e5b25be4120201574018e1d54b45 Mon Sep 17 00:00:00 2001 From: "Robert P. J. Day" Date: Wed, 18 Jun 2014 16:46:50 +0300 Subject: bitbake: bitbake-user-manual-intro.xml: Basic proofreading, grammar fixes. (Bitbake rev: 266a0b5ef41dcc4048e2a4d1c43567568d7449d7) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- .../bitbake-user-manual-intro.xml | 44 ++++++++++++++++------ 1 file changed, 32 insertions(+), 12 deletions(-) (limited to 'bitbake/doc') diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml index ae267b42c8..330bfbd3c3 100644 --- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml +++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml @@ -10,7 +10,7 @@ The information attempts to be as independent as possible regarding systems that use BitBake, such as the Yocto Project and OpenEmbedded. - In some cases, scenarios or examples that within the context of + In some cases, scenarios or examples within the context of a build system are used in the manual to help with understanding. For these cases, the manual clearly states the context. @@ -36,6 +36,7 @@ BitBake executes tasks according to provided metadata that builds up the tasks. Metadata is stored in recipe (.bb), + recipe "append" (.bbappend), configuration (.conf), and class (.bbclass) files and provides BitBake with instructions on what tasks to run and @@ -44,11 +45,11 @@ BitBake includes a fetcher library for obtaining source code from various places such as source control - systems or websites. + systems, websites, or local files. The instructions for each unit to be built (e.g. a piece - of software) are known as recipe files and + of software) are known as "recipe" files and contain all the information about the unit (dependencies, source file locations, checksums, description and so on). @@ -69,7 +70,7 @@ BitBake was originally a part of the OpenEmbedded project. It was inspired by the Portage package management system used by the Gentoo Linux distribution. - On December 7, 2004, OpenEmbedded project team member, + On December 7, 2004, OpenEmbedded project team member Chris Larson split the project into two distinct pieces: BitBake, a generic task executor @@ -138,7 +139,7 @@ projects for their builds. - Provide an inheritance mechanism that share + Provide an inheritance mechanism to share common metadata between many packages. @@ -178,14 +179,14 @@ what tasks are required to run, and executes those tasks. Similar to GNU Make, BitBake controls how software is built. - GNU Make achieves its control through "makefiles". + GNU Make achieves its control through "makefiles", while BitBake uses "recipes". BitBake extends the capabilities of a simple - tool like GNU Make by allowing for much more complex tasks - to be completed, such as assembling entire embedded Linux + tool like GNU Make by allowing for the definition of much more + complex tasks, such as assembling entire embedded Linux distributions. @@ -203,12 +204,15 @@ .bb, are the most basic metadata files. These recipe files provide BitBake with the following: - Descriptive information about the package + Descriptive information about the + package (author, homepage, license, and so on) The version of the recipe - Existing Dependencies + Existing dependencies (both build + and runtime dependencies) Where the source code resides Whether the source code requires any patches - How to compile the source code + How to configure and compile the + source code Where on the target machine to install the package being compiled @@ -284,7 +288,8 @@ To illustrate how you can use layers to keep things modular, consider customizations you might make to support a specific target machine. These types of customizations typically reside in a special layer, - rather than a general layer, called a Board Specific Package (BSP) Layer. + rather than a general layer, called a Board Support Package (BSP) + Layer. Furthermore, the machine customizations should be isolated from recipes and metadata that support a new GUI environment, for example. @@ -413,6 +418,21 @@ you have a directory entitled bitbake-1.17.0. + Using the BitBake that comes with your + build checkout: + A final possibility for getting a copy of BitBake is that it + already comes with your checkout of a larger Bitbake-based build + system, such as Poky or Yocto Project. + Rather than manually checking out individual layers and + gluing them together yourself, you can check + out an entire build system such as Poky with something like: + + $ git clone git://git.yoctoproject.org/poky + + The checkout will already include a version of BitBake that + has been thoroughly tested for compatibility with the other + components. + -- cgit v1.2.3-54-g00ecf