diff options
author | Scott Rifenbark <srifenbark@gmail.com> | 2018-01-29 15:18:03 -0800 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2018-02-14 15:25:29 +0000 |
commit | ae06e04cd225d2c2147ca355e2dd39b4f6cf6775 (patch) | |
tree | c920e85262a91e7626279e7dcbbd56a299919f49 /documentation/getting-started/eclipse/html/getting-started/configuration-and-compilation-dev-environment.html | |
parent | ebc7de094881dd8f2450aa4fdf548f2e9c835df1 (diff) | |
download | poky-ae06e04cd225d2c2147ca355e2dd39b4f6cf6775.tar.gz |
documentation: Created new "Getting Started" manual.
Creation involved removing the overview-manual and replacing it
with the getting-started manual. All links to the string
"&YOCTO_DOCS_OVERVIEW_URL" had to be replaced with
"&YOCTO_DOCS_GS_URL" across the entire YP manual set. I renamed
files used to create the manual with prefixes suited for the
new manual name, which is "Getting Started With Yocto Project".
The style sheet for the new manual needed updating to display the
new .PNG image for the title page. The mega-manual file had to
be updated to include the files. The mega-manual.sed file had
to be updated to include the new manual and not use the overview
manual.
(From yocto-docs rev: 6c7abf9192390121000f577d6c98f259d290d15d)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/getting-started/eclipse/html/getting-started/configuration-and-compilation-dev-environment.html')
-rw-r--r-- | documentation/getting-started/eclipse/html/getting-started/configuration-and-compilation-dev-environment.html | 93 |
1 files changed, 93 insertions, 0 deletions
diff --git a/documentation/getting-started/eclipse/html/getting-started/configuration-and-compilation-dev-environment.html b/documentation/getting-started/eclipse/html/getting-started/configuration-and-compilation-dev-environment.html new file mode 100644 index 0000000000..9a94cc47da --- /dev/null +++ b/documentation/getting-started/eclipse/html/getting-started/configuration-and-compilation-dev-environment.html | |||
@@ -0,0 +1,93 @@ | |||
1 | <html> | ||
2 | <head> | ||
3 | <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> | ||
4 | <title>2.8.5.3. Configuration and Compilation</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="bitbake-dev-environment.html" title="2.8.5. BitBake"> | ||
9 | <link rel="prev" href="patching-dev-environment.html" title="2.8.5.2. Patching"> | ||
10 | <link rel="next" href="package-splitting-dev-environment.html" title="2.8.5.4. Package Splitting"> | ||
11 | </head> | ||
12 | <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.8.5.3. Configuration and Compilation"> | ||
13 | <div class="titlepage"><div><div><h4 class="title"> | ||
14 | <a name="configuration-and-compilation-dev-environment"></a>2.8.5.3. Configuration and Compilation</h4></div></div></div> | ||
15 | <p> | ||
16 | After source code is patched, BitBake executes tasks that | ||
17 | configure and compile the source code: | ||
18 | </p> | ||
19 | <table border="0" summary="manufactured viewport for HTML img" cellspacing="0" cellpadding="0" width="630"><tr style="height: 450px"><td align="center"><img src="figures/configuration-compile-autoreconf.png" align="middle" width="630"></td></tr></table> | ||
20 | <p> | ||
21 | </p> | ||
22 | <p> | ||
23 | This step in the build process consists of three tasks: | ||
24 | </p> | ||
25 | <div class="itemizedlist"><ul class="itemizedlist" type="disc"> | ||
26 | <li class="listitem"><p> | ||
27 | <span class="emphasis"><em><a class="link" href="../ref-manual/ref-tasks-prepare_recipe_sysroot.html" target="_self"><code class="filename">do_prepare_recipe_sysroot</code></a>:</em></span> | ||
28 | This task sets up the two sysroots in | ||
29 | <code class="filename">${</code><a class="link" href="../ref-manual/var-WORKDIR.html" target="_self"><code class="filename">WORKDIR</code></a><code class="filename">}</code> | ||
30 | (i.e. <code class="filename">recipe-sysroot</code> and | ||
31 | <code class="filename">recipe-sysroot-native</code>) so that | ||
32 | the sysroots contain the contents of the | ||
33 | <a class="link" href="../ref-manual/ref-tasks-populate_sysroot.html" target="_self"><code class="filename">do_populate_sysroot</code></a> | ||
34 | tasks of the recipes on which the recipe | ||
35 | containing the tasks depends. | ||
36 | A sysroot exists for both the target and for the native | ||
37 | binaries, which run on the host system. | ||
38 | </p></li> | ||
39 | <li class="listitem"> | ||
40 | <p><span class="emphasis"><em><code class="filename">do_configure</code>:</em></span> | ||
41 | This task configures the source by enabling and | ||
42 | disabling any build-time and configuration options for | ||
43 | the software being built. | ||
44 | Configurations can come from the recipe itself as well | ||
45 | as from an inherited class. | ||
46 | Additionally, the software itself might configure itself | ||
47 | depending on the target for which it is being built. | ||
48 | </p> | ||
49 | <p>The configurations handled by the | ||
50 | <a class="link" href="../ref-manual/ref-tasks-configure.html" target="_self"><code class="filename">do_configure</code></a> | ||
51 | task are specific | ||
52 | to source code configuration for the source code | ||
53 | being built by the recipe.</p> | ||
54 | <p>If you are using the | ||
55 | <a class="link" href="../ref-manual/ref-classes-autotools.html" target="_self"><code class="filename">autotools</code></a> | ||
56 | class, | ||
57 | you can add additional configuration options by using | ||
58 | the | ||
59 | <a class="link" href="../ref-manual/var-EXTRA_OECONF.html" target="_self"><code class="filename">EXTRA_OECONF</code></a> | ||
60 | or | ||
61 | <a class="link" href="../ref-manual/var-PACKAGECONFIG_CONFARGS.html" target="_self"><code class="filename">PACKAGECONFIG_CONFARGS</code></a> | ||
62 | variables. | ||
63 | For information on how this variable works within | ||
64 | that class, see the | ||
65 | <code class="filename">meta/classes/autotools.bbclass</code> file. | ||
66 | </p> | ||
67 | </li> | ||
68 | <li class="listitem"><p><span class="emphasis"><em><code class="filename">do_compile</code>:</em></span> | ||
69 | Once a configuration task has been satisfied, BitBake | ||
70 | compiles the source using the | ||
71 | <a class="link" href="../ref-manual/ref-tasks-compile.html" target="_self"><code class="filename">do_compile</code></a> | ||
72 | task. | ||
73 | Compilation occurs in the directory pointed to by the | ||
74 | <a class="link" href="../ref-manual/var-B.html" target="_self"><code class="filename">B</code></a> | ||
75 | variable. | ||
76 | Realize that the <code class="filename">B</code> directory is, by | ||
77 | default, the same as the | ||
78 | <a class="link" href="../ref-manual/var-S.html" target="_self"><code class="filename">S</code></a> | ||
79 | directory.</p></li> | ||
80 | <li class="listitem"><p><span class="emphasis"><em><code class="filename">do_install</code>:</em></span> | ||
81 | Once compilation is done, BitBake executes the | ||
82 | <a class="link" href="../ref-manual/ref-tasks-install.html" target="_self"><code class="filename">do_install</code></a> | ||
83 | task. | ||
84 | This task copies files from the <code class="filename">B</code> | ||
85 | directory and places them in a holding area pointed to | ||
86 | by the | ||
87 | <a class="link" href="../ref-manual/var-D.html" target="_self"><code class="filename">D</code></a> | ||
88 | variable.</p></li> | ||
89 | </ul></div> | ||
90 | <p> | ||
91 | </p> | ||
92 | </div></body> | ||
93 | </html> | ||