diff options
Diffstat (limited to 'documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components-bitbake.html')
-rw-r--r-- | documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components-bitbake.html | 66 |
1 files changed, 0 insertions, 66 deletions
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components-bitbake.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components-bitbake.html deleted file mode 100644 index 184ffdbd2c..0000000000 --- a/documentation/ref-manual/eclipse/html/poky-ref-manual/usingpoky-components-bitbake.html +++ /dev/null | |||
@@ -1,66 +0,0 @@ | |||
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="The Yocto Project Reference Manual"> | ||
8 | <link rel="up" href="usingpoky-components.html" title="3.1. Yocto Project Components"> | ||
9 | <link rel="prev" href="usingpoky-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 system and is responsible | ||
17 | for parsing the metadata, generating a list of tasks from it, | ||
18 | and then executing those tasks. | ||
19 | To see a list of the options BitBake supports, use the following help command: | ||
20 | </p> | ||
21 | <pre class="literallayout"> | ||
22 | $ bitbake --help | ||
23 | </pre> | ||
24 | <p> | ||
25 | </p> | ||
26 | <p> | ||
27 | The most common usage for BitBake is <code class="filename">bitbake <packagename></code>, where | ||
28 | <code class="filename">packagename</code> is the name of the package you want to build | ||
29 | (referred to as the "target" in this manual). | ||
30 | The target often equates to the first part of a <code class="filename">.bb</code> filename. | ||
31 | So, to run the <code class="filename">matchbox-desktop_1.2.3.bb</code> file, you | ||
32 | might type the following: | ||
33 | </p> | ||
34 | <pre class="literallayout"> | ||
35 | $ bitbake matchbox-desktop | ||
36 | </pre> | ||
37 | <p> | ||
38 | Several different versions of <code class="filename">matchbox-desktop</code> might exist. | ||
39 | BitBake chooses the one selected by the distribution configuration. | ||
40 | You can get more details about how BitBake chooses between different | ||
41 | target versions and providers in the | ||
42 | "<a class="link" href="ref-bitbake-providers.html" title="6.2. Preferences and Providers">Preferences and Providers</a>" section. | ||
43 | </p> | ||
44 | <p> | ||
45 | BitBake also tries to execute any dependent tasks first. | ||
46 | So for example, before building <code class="filename">matchbox-desktop</code>, BitBake | ||
47 | would build a cross compiler and <code class="filename">eglibc</code> if they had not already | ||
48 | been built. | ||
49 | </p> | ||
50 | <div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"> | ||
51 | <h3 class="title">Note</h3>This release of the Yocto Project does not support the <code class="filename">glibc</code> | ||
52 | GNU version of the Unix standard C library. By default, the OpenEmbedded build system | ||
53 | builds with <code class="filename">eglibc</code>.</div> | ||
54 | <p> | ||
55 | </p> | ||
56 | <p> | ||
57 | A useful BitBake option to consider is the <code class="filename">-k</code> or | ||
58 | <code class="filename">--continue</code> option. | ||
59 | This option instructs BitBake to try and continue processing the job as much | ||
60 | as possible even after encountering an error. | ||
61 | When an error occurs, the target that | ||
62 | failed and those that depend on it cannot be remade. | ||
63 | However, when you use this option other dependencies can still be processed. | ||
64 | </p> | ||
65 | </div></body> | ||
66 | </html> | ||