On Thu, 2018-11-29 at 14:21 +0200, Mikko Rapeli wrote: > If IMAGE_ROOTFS_SIZE_LIMIT is defined in image configuration, then > build will fail if for tar image type the uncompressed tar ball size > exceeds the value, as reported by 'du -ks'. > > This check could be extended to other image types as well. > > There already exists a check with IMAGE_ROOTFS_SIZE variable > but I could not figure out how to actually use it. It does > some quite complex overhead calculations which did not seem > to work for me on sumo. > > When the image size is exceeded, build fails like this: > > ERROR: image-1.0-r0 do_image_tar: Image size 170712 of > /home/builder/src/base/build/tmp/work/linux/image/1.0-r0/deploy- > image-complete/image.rootfs.tar reported by 'du -ks' is larger than > limit IMAGE_ROOTFS_SIZE_LIMIT 170000
What about IMAGE_ROOTFS_MAXSIZE? I think IMAGE_ROOTFS_SIZE is about adding extra space to the image, not limiting its size... Cheers, Richard -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
