diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-08-13 12:57:01 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-08-14 09:34:58 +0100 |
commit | efcb0a81d8ab5d8e250c677cd6919b19172683d1 (patch) | |
tree | 0f1a827d58b2bf8c98927c5251523fe816e24c5d /documentation/poky-ref-manual/ref-structure.xml | |
parent | 49e8c5aa6d7e3ea80e8e728b8d12313cf55f87b7 (diff) | |
download | ast2050-yocto-poky-efcb0a81d8ab5d8e250c677cd6919b19172683d1.zip ast2050-yocto-poky-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>
Diffstat (limited to 'documentation/poky-ref-manual/ref-structure.xml')
-rw-r--r-- | documentation/poky-ref-manual/ref-structure.xml | 25 |
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 8f70553..2db58dd 100644 --- a/documentation/poky-ref-manual/ref-structure.xml +++ b/documentation/poky-ref-manual/ref-structure.xml @@ -329,14 +329,27 @@ This directory receives complete filesystem images. If you want to flash the resulting image from a build onto a device, look here for the image. </para> - + + <para> + Be careful when deleting files in this directory. + You can safely delete old images from this directory (e.g. + <filename>core-image-*</filename>, <filename>hob-image-*</filename>, + etc.). + However, the kernel (<filename>*zImage*</filename>, <filename>*uImage*</filename>, etc.), + bootloader and other supplementary files might be deployed here prior to building an + image. + Because these files, however, are not directly produced from the image, if you + delete them they will not be automatically re-created when you build the image again. + </para> + <para> - Note, you should not remove any files from this directory by hand in an attempt - to rebuild an image. - If you want to clean out the cache, re-run the build using the following - BitBake command: + If you do accidentally delete files here, you will need to force them to be + re-created. + In order to do that, you will need to know the target that produced them. + For example, these commands rebuild and re-create the kernel files: <literallayout class='monospaced'> - $ bitbake -c cleanall <target> + $ bitbake -c clean virtual/kernel + $ bitbake virtual/kernel </literallayout> </para> </section> |