Ok, thanks Giovanni --
Dott. Ing. Giovanni Foiani Cell: +39-349-3577515 Phone: +39-0532-97-4106 mail: giovanni.foi...@unife.it CenTec - Corso Guercino, 47 - 44042 Cento (FE) On Mon, Jul 30, 2012 at 4:42 PM, Paul Eggleton < paul.eggle...@linux.intel.com> wrote: > On Monday 30 July 2012 15:18:37 Giovanni Foiani wrote: > > I read this section in Poky Reference manual: > > > > *A.2.13. build/tmp/deploy/images/* > > * > > * > > *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.* > > * > > * > > *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: * > > * $ bitbake -c cleanall <target>* > > > > I built many images using hob and in my *build/tmp/deploy/images/ *folder > > there are a lot of rootfs images (like > > hob-image-imx53qsb-<timestamp>.rootfs.ext3 etc..) and I want to remove > the > > unused ones to free some space.. > > > > I tried tp run: > > > > *bitbake -c cleanall * hob-image-imx53qsb-<timestamp> > > > > but I got: > > ERROR: Nothing PROVIDES 'hob-image-imx53qsb-<timestamp>' > > I'm not sure where this came from originally, but it is not correct. I'll > talk > to Scott R about fixing this part of the manual. > > > Can I safely remove these files by hand? > > The hob-image-*, yes. In fact any actual image files in deploy/images are > OK to > delete (excluding *zImage*, *uImage*, etc. - those are kernels). All the > warnings are trying to prevent is people deleting the entire contents of > deploy/images and then wondering why the kernel, bootloader etc. that get > produced as part of the process of building an image but are not part of > the > image itself aren't re-created when they build the image again afterwards. > > Cheers, > Paul > > -- > > Paul Eggleton > Intel Open Source Technology Centre >
_______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
