summaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-images.html
diff options
context:
space:
mode:
authorTimo Mueller <timo.mueller@bmw-carit.de>2013-02-08 09:16:33 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-02-14 17:25:35 +0000
commita41a805500cab281fba15bd8e5d3e60b88d0d4be (patch)
tree9973678912b57cfdef5b1f9676794a556b4d8966 /documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-images.html
parent768152340898cbb9faed6e8865a4e35c69833230 (diff)
downloadpoky-a41a805500cab281fba15bd8e5d3e60b88d0d4be.tar.gz
documentation: Part 1 of 2 updates to integrating docs to Eclipse help.
Hi, the generation of eclipse help files has been merged from the timo branch to the master. Since the creation of the timo branch there have been some changes to the master branch (e.g. new documentation, renamed documentation). This patch set does some cleanup for the renamed documentation and adds eclipse help generation support to the new documentation. 01: Removes the 'the' from the document titles 02..04: Cleanup obsolete artifacts resulting from the merge 05..08: Add eclipse help generation for ref-manual 09..13: Add eclipse help generation for kernel-dev 14..18: Add eclipse help generation for profile-manual Best regards, Timo This patch set originally contained 18 patches. I (Scott Rifenbark) had to push these changes as two parts. This is the first part. It does not include creation of the three cusomization files. (From yocto-docs rev: 9b1889f6e31ee70dae704fa08763fb9196616dad) 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-deploy-images.html')
-rw-r--r--documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-images.html44
1 files changed, 0 insertions, 44 deletions
diff --git a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-images.html b/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-images.html
deleted file mode 100644
index b2810d2a76..0000000000
--- a/documentation/ref-manual/eclipse/html/poky-ref-manual/structure-build-tmp-deploy-images.html
+++ /dev/null
@@ -1,44 +0,0 @@
1<html>
2<head>
3<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
4<title>5.2.14. build/tmp/deploy/images/</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-deploy-licenses.html" title="5.2.13. build/tmp/deploy/licenses/">
10<link rel="next" href="structure-build-tmp-deploy-ipk.html" title="5.2.15. build/tmp/deploy/ipk/">
11</head>
12<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="section" title="5.2.14. build/tmp/deploy/images/">
13<div class="titlepage"><div><div><h3 class="title">
14<a name="structure-build-tmp-deploy-images"></a>5.2.14. <code class="filename">build/tmp/deploy/images/</code>
15</h3></div></div></div>
16<p>
17 This directory receives complete filesystem images.
18 If you want to flash the resulting image from a build onto a device, look here for the image.
19 </p>
20<p>
21 Be careful when deleting files in this directory.
22 You can safely delete old images from this directory (e.g.
23 <code class="filename">core-image-*</code>, <code class="filename">hob-image-*</code>,
24 etc.).
25 However, the kernel (<code class="filename">*zImage*</code>, <code class="filename">*uImage*</code>, etc.),
26 bootloader and other supplementary files might be deployed here prior to building an
27 image.
28 Because these files, however, are not directly produced from the image, if you
29 delete them they will not be automatically re-created when you build the image again.
30 </p>
31<p>
32 If you do accidentally delete files here, you will need to force them to be
33 re-created.
34 In order to do that, you will need to know the target that produced them.
35 For example, these commands rebuild and re-create the kernel files:
36 </p>
37<pre class="literallayout">
38 $ bitbake -c clean virtual/kernel
39 $ bitbake virtual/kernel
40 </pre>
41<p>
42 </p>
43</div></body>
44</html>