summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-work.html
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-12-11 12:07:58 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-01-07 14:43:25 +0000
commited0a240e1632682ec4c33341f3e24ad71773cdfc (patch)
tree201557f498b77b9f51fad7e12a6009f74aca4c65 /documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-work.html
parentaf19d889ef320f9625aae42eed6688b5cc739793 (diff)
downloadpoky-ed0a240e1632682ec4c33341f3e24ad71773cdfc.tar.gz
documentation: Rename of poky-ref-manual folder to ref-manual.
Changing the folder that holds the YP Reference Manual to be "ref-manual". This will help with confustion over the manual's intended purpose. (From yocto-docs rev: 1106442964b5080cb0b6b3bd3af32e9407c0f7c1) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-work.html')
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-work.html52
1 files changed, 52 insertions, 0 deletions
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-work.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-work.html
new file mode 100644
index 0000000000..aa78c18b5d
--- /dev/null
+++ b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-work.html
@@ -0,0 +1,52 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.2.20. build/tmp/work/</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="structure-build.html" title="5.2. The Build Directory - build/">
9<link rel="prev" href="structure-build-tmp-pkgdata.html" title="5.2.19. build/tmp/pkgdata/">
10<link rel="next" href="structure-meta.html" title="5.3. The Metadata - meta/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.20. build/tmp/work/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-build-tmp-work"></a>5.2.20. <code class="filename">build/tmp/work/</code>
15</h3></div></div></div>
16<p>
17 This directory contains architecture-specific work sub-directories for packages built by BitBake.
18 All tasks execute from a work directory.
19 For example, the source for a particular package is unpacked, patched, configured and compiled all
20 within its own work directory.
21 Within the work directory, organization is based on the package group for which the source
22 is being compiled.
23 </p>
24<p>
25 It is worth considering the structure of a typical work directory.
26 As an example, consider the <code class="filename">linux-yocto-kernel-3.0</code>
27 on the machine <code class="filename">qemux86</code>
28 built within the Yocto Project.
29 For this package, a work directory of
30 <code class="filename">tmp/work/qemux86-poky-linux/linux-yocto-3.0+git1+&lt;.....&gt;</code>,
31 referred to as <code class="filename"><a class="link" href="ref-variables-glos.html#var-WORKDIR" title="WORKDIR">WORKDIR</a></code>, is created.
32 Within this directory, the source is unpacked to
33 <code class="filename">linux-qemux86-standard-build</code> and then patched by Quilt
34 (see the
35 "<a class="link" href="../dev-manual/using-a-quilt-workflow.html" target="_self">Modifying Package
36 Source Code with Quilt</a>" section in the Yocto Project Development Manual.
37 Within the <code class="filename">linux-qemux86-standard-build</code> directory,
38 standard Quilt directories <code class="filename">linux-3.0/patches</code>
39 and <code class="filename">linux-3.0/.pc</code> are created,
40 and standard Quilt commands can be used.
41 </p>
42<p>
43 There are other directories generated within WORKDIR.
44 The most important directory is WORKDIR<code class="filename">/temp/</code>, which has log files for each
45 task (<code class="filename">log.do_*.pid</code>) and contains the scripts BitBake runs for
46 each task (<code class="filename">run.do_*.pid</code>).
47 The WORKDIR<code class="filename">/image/</code> directory is where "make
48 install" places its output that is then split into sub-packages
49 within WORKDIR<code class="filename">/packages-split/</code>.
50 </p>
51</div></body>
52</html>