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/source-fetching-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/source-fetching-dev-environment.html')
-rw-r--r-- | documentation/getting-started/eclipse/html/getting-started/source-fetching-dev-environment.html | 93 |
1 files changed, 93 insertions, 0 deletions
diff --git a/documentation/getting-started/eclipse/html/getting-started/source-fetching-dev-environment.html b/documentation/getting-started/eclipse/html/getting-started/source-fetching-dev-environment.html new file mode 100644 index 0000000000..afcdafdc76 --- /dev/null +++ b/documentation/getting-started/eclipse/html/getting-started/source-fetching-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.1. Source Fetching</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="bitbake-dev-environment.html" title="2.8.5. BitBake"> | ||
10 | <link rel="next" href="patching-dev-environment.html" title="2.8.5.2. Patching"> | ||
11 | </head> | ||
12 | <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="2.8.5.1. Source Fetching"> | ||
13 | <div class="titlepage"><div><div><h4 class="title"> | ||
14 | <a name="source-fetching-dev-environment"></a>2.8.5.1. Source Fetching</h4></div></div></div> | ||
15 | <p> | ||
16 | The first stages of building a recipe are to fetch and unpack | ||
17 | the source code: | ||
18 | </p> | ||
19 | <table border="0" summary="manufactured viewport for HTML img" cellspacing="0" cellpadding="0" width="585"><tr style="height: 450px"><td align="center"><img src="figures/source-fetching.png" align="middle" width="585"></td></tr></table> | ||
20 | <p> | ||
21 | </p> | ||
22 | <p> | ||
23 | The | ||
24 | <a class="link" href="../ref-manual/ref-tasks-fetch.html" target="_self"><code class="filename">do_fetch</code></a> | ||
25 | and | ||
26 | <a class="link" href="../ref-manual/ref-tasks-unpack.html" target="_self"><code class="filename">do_unpack</code></a> | ||
27 | tasks fetch the source files and unpack them into the work | ||
28 | directory. | ||
29 | </p> | ||
30 | <div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"> | ||
31 | <h3 class="title">Note</h3> | ||
32 | For every local file (e.g. <code class="filename">file://</code>) | ||
33 | that is part of a recipe's | ||
34 | <a class="link" href="../ref-manual/var-SRC_URI.html" target="_self"><code class="filename">SRC_URI</code></a> | ||
35 | statement, the OpenEmbedded build system takes a checksum | ||
36 | of the file for the recipe and inserts the checksum into | ||
37 | the signature for the <code class="filename">do_fetch</code>. | ||
38 | If any local file has been modified, the | ||
39 | <code class="filename">do_fetch</code> task and all tasks that | ||
40 | depend on it are re-executed. | ||
41 | </div> | ||
42 | <p> | ||
43 | By default, everything is accomplished in the | ||
44 | <a class="link" href="../ref-manual/build-directory.html" target="_self">Build Directory</a>, | ||
45 | which has a defined structure. | ||
46 | For additional general information on the Build Directory, | ||
47 | see the | ||
48 | "<a class="link" href="../ref-manual/structure-core-build.html" target="_self"><code class="filename">build/</code></a>" | ||
49 | section in the Yocto Project Reference Manual. | ||
50 | </p> | ||
51 | <p> | ||
52 | Unpacked source files are pointed to by the | ||
53 | <a class="link" href="../ref-manual/var-S.html" target="_self"><code class="filename">S</code></a> | ||
54 | variable. | ||
55 | Each recipe has an area in the Build Directory where the | ||
56 | unpacked source code resides. | ||
57 | The name of that directory for any given recipe is defined from | ||
58 | several different variables. | ||
59 | You can see the variables that define these directories | ||
60 | by looking at the figure: | ||
61 | </p> | ||
62 | <div class="itemizedlist"><ul class="itemizedlist" type="disc"> | ||
63 | <li class="listitem"><p><a class="link" href="../ref-manual/var-TMPDIR.html" target="_self"><code class="filename">TMPDIR</code></a> - | ||
64 | The base directory where the OpenEmbedded build system | ||
65 | performs all its work during the build. | ||
66 | </p></li> | ||
67 | <li class="listitem"><p><a class="link" href="../ref-manual/var-PACKAGE_ARCH.html" target="_self"><code class="filename">PACKAGE_ARCH</code></a> - | ||
68 | The architecture of the built package or packages. | ||
69 | </p></li> | ||
70 | <li class="listitem"><p><a class="link" href="../ref-manual/var-TARGET_OS.html" target="_self"><code class="filename">TARGET_OS</code></a> - | ||
71 | The operating system of the target device. | ||
72 | </p></li> | ||
73 | <li class="listitem"><p><a class="link" href="../ref-manual/var-PN.html" target="_self"><code class="filename">PN</code></a> - | ||
74 | The name of the built package. | ||
75 | </p></li> | ||
76 | <li class="listitem"><p><a class="link" href="../ref-manual/var-PV.html" target="_self"><code class="filename">PV</code></a> - | ||
77 | The version of the recipe used to build the package. | ||
78 | </p></li> | ||
79 | <li class="listitem"><p><a class="link" href="../ref-manual/var-PR.html" target="_self"><code class="filename">PR</code></a> - | ||
80 | The revision of the recipe used to build the package. | ||
81 | </p></li> | ||
82 | <li class="listitem"><p><a class="link" href="../ref-manual/var-WORKDIR.html" target="_self"><code class="filename">WORKDIR</code></a> - | ||
83 | The location within <code class="filename">TMPDIR</code> where | ||
84 | a specific package is built. | ||
85 | </p></li> | ||
86 | <li class="listitem"><p><a class="link" href="../ref-manual/var-S.html" target="_self"><code class="filename">S</code></a> - | ||
87 | Contains the unpacked source files for a given recipe. | ||
88 | </p></li> | ||
89 | </ul></div> | ||
90 | <p> | ||
91 | </p> | ||
92 | </div></body> | ||
93 | </html> | ||