diff options
Diffstat (limited to 'documentation/getting-started/eclipse/html/getting-started/usingpoky-components-bitbake.html')
| -rw-r--r-- | documentation/getting-started/eclipse/html/getting-started/usingpoky-components-bitbake.html | 82 |
1 files changed, 82 insertions, 0 deletions
diff --git a/documentation/getting-started/eclipse/html/getting-started/usingpoky-components-bitbake.html b/documentation/getting-started/eclipse/html/getting-started/usingpoky-components-bitbake.html new file mode 100644 index 0000000000..39fa32b154 --- /dev/null +++ b/documentation/getting-started/eclipse/html/getting-started/usingpoky-components-bitbake.html | |||
| @@ -0,0 +1,82 @@ | |||
| 1 | <html> | ||
| 2 | <head> | ||
| 3 | <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> | ||
| 4 | <title>3.1.1. BitBake</title> | ||
| 5 | <link rel="stylesheet" type="text/css" href="../book.css"> | ||
| 6 | <meta name="generator" content="DocBook XSL Stylesheets V1.76.1"> | ||
| 7 | <link rel="home" href="index.html" title="Getting Started With Yocto Project"> | ||
| 8 | <link rel="up" href="yocto-project-components.html" title="3.1. Yocto Project Components"> | ||
| 9 | <link rel="prev" href="yocto-project-components.html" title="3.1. Yocto Project Components"> | ||
| 10 | <link rel="next" href="usingpoky-components-metadata.html" title="3.1.2. Metadata (Recipes)"> | ||
| 11 | </head> | ||
| 12 | <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="3.1.1. BitBake"> | ||
| 13 | <div class="titlepage"><div><div><h3 class="title"> | ||
| 14 | <a name="usingpoky-components-bitbake"></a>3.1.1. BitBake</h3></div></div></div> | ||
| 15 | <p> | ||
| 16 | BitBake is the tool at the heart of the OpenEmbedded build | ||
| 17 | system and is responsible for parsing the | ||
| 18 | <a class="link" href="../ref-manual/metadata.html" target="_self">Metadata</a>, | ||
| 19 | generating a list of tasks from it, and then executing those | ||
| 20 | tasks. | ||
| 21 | </p> | ||
| 22 | <p> | ||
| 23 | This section briefly introduces BitBake. | ||
| 24 | If you want more information on BitBake, see the | ||
| 25 | <a class="link" href="../bitbake-user-manual/bitbake-user-manual.html" target="_self">BitBake User Manual</a>. | ||
| 26 | </p> | ||
| 27 | <p> | ||
| 28 | To see a list of the options BitBake supports, use either of | ||
| 29 | the following commands: | ||
| 30 | </p> | ||
| 31 | <pre class="literallayout"> | ||
| 32 | $ bitbake -h | ||
| 33 | $ bitbake --help | ||
| 34 | </pre> | ||
| 35 | <p> | ||
| 36 | </p> | ||
| 37 | <p> | ||
| 38 | The most common usage for BitBake is | ||
| 39 | <code class="filename">bitbake <em class="replaceable"><code>packagename</code></em></code>, | ||
| 40 | where <code class="filename">packagename</code> is the name of the | ||
| 41 | package you want to build (referred to as the "target" in this | ||
| 42 | manual). | ||
| 43 | The target often equates to the first part of a recipe's | ||
| 44 | filename (e.g. "foo" for a recipe named | ||
| 45 | <code class="filename">foo_1.3.0-r0.bb</code>). | ||
| 46 | So, to process the | ||
| 47 | <code class="filename">matchbox-desktop_1.2.3.bb</code> recipe file, you | ||
| 48 | might type the following: | ||
| 49 | </p> | ||
| 50 | <pre class="literallayout"> | ||
| 51 | $ bitbake matchbox-desktop | ||
| 52 | </pre> | ||
| 53 | <p> | ||
| 54 | Several different versions of | ||
| 55 | <code class="filename">matchbox-desktop</code> might exist. | ||
| 56 | BitBake chooses the one selected by the distribution | ||
| 57 | configuration. | ||
| 58 | You can get more details about how BitBake chooses between | ||
| 59 | different target versions and providers in the | ||
| 60 | "<a class="link" href="../bitbake-user-manual/bb-bitbake-preferences.html" target="_self">Preferences</a>" | ||
| 61 | section of the BitBake User Manual. | ||
| 62 | </p> | ||
| 63 | <p> | ||
| 64 | BitBake also tries to execute any dependent tasks first. | ||
| 65 | So for example, before building | ||
| 66 | <code class="filename">matchbox-desktop</code>, BitBake would build a | ||
| 67 | cross compiler and <code class="filename">glibc</code> if they had not | ||
| 68 | already been built. | ||
| 69 | </p> | ||
| 70 | <p> | ||
| 71 | A useful BitBake option to consider is the | ||
| 72 | <code class="filename">-k</code> or <code class="filename">--continue</code> | ||
| 73 | option. | ||
| 74 | This option instructs BitBake to try and continue processing | ||
| 75 | the job as long as possible even after encountering an error. | ||
| 76 | When an error occurs, the target that failed and those that | ||
| 77 | depend on it cannot be remade. | ||
| 78 | However, when you use this option other dependencies can | ||
| 79 | still be processed. | ||
| 80 | </p> | ||
| 81 | </div></body> | ||
| 82 | </html> | ||