summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2012-08-13 12:57:01 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-08-14 09:34:58 +0100
commitefcb0a81d8ab5d8e250c677cd6919b19172683d1 (patch)
tree0f1a827d58b2bf8c98927c5251523fe816e24c5d
parent49e8c5aa6d7e3ea80e8e728b8d12313cf55f87b7 (diff)
downloadpoky-efcb0a81d8ab5d8e250c677cd6919b19172683d1.tar.gz
documentation/poky-ref-manual/ref-structure.xml: deleting images
Added clarification on how a user can hand-delete images from the build/tmp/deply/images directory. (From yocto-docs rev: 4655085d43b36b024a2e01cfcc7455e18d891ab8) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/poky-ref-manual/ref-structure.xml25
1 files changed, 19 insertions, 6 deletions
diff --git a/documentation/poky-ref-manual/ref-structure.xml b/documentation/poky-ref-manual/ref-structure.xml
index 8f705537c4..2db58ddaef 100644
--- a/documentation/poky-ref-manual/ref-structure.xml
+++ b/documentation/poky-ref-manual/ref-structure.xml
@@ -329,14 +329,27 @@
329 This directory receives complete filesystem images. 329 This directory receives complete filesystem images.
330 If you want to flash the resulting image from a build onto a device, look here for the image. 330 If you want to flash the resulting image from a build onto a device, look here for the image.
331 </para> 331 </para>
332 332
333 <para>
334 Be careful when deleting files in this directory.
335 You can safely delete old images from this directory (e.g.
336 <filename>core-image-*</filename>, <filename>hob-image-*</filename>,
337 etc.).
338 However, the kernel (<filename>*zImage*</filename>, <filename>*uImage*</filename>, etc.),
339 bootloader and other supplementary files might be deployed here prior to building an
340 image.
341 Because these files, however, are not directly produced from the image, if you
342 delete them they will not be automatically re-created when you build the image again.
343 </para>
344
333 <para> 345 <para>
334 Note, you should not remove any files from this directory by hand in an attempt 346 If you do accidentally delete files here, you will need to force them to be
335 to rebuild an image. 347 re-created.
336 If you want to clean out the cache, re-run the build using the following 348 In order to do that, you will need to know the target that produced them.
337 BitBake command: 349 For example, these commands rebuild and re-create the kernel files:
338 <literallayout class='monospaced'> 350 <literallayout class='monospaced'>
339 $ bitbake -c cleanall &lt;target&gt; 351 $ bitbake -c clean virtual/kernel
352 $ bitbake virtual/kernel
340 </literallayout> 353 </literallayout>
341 </para> 354 </para>
342 </section> 355 </section>