[yocto] per-image ROOTFS sizes

[Trevor Woerner]

On Wed, Dec 12, 2012 at 3:19 PM, Darren Hart <dvhart at linux.intel.com> wrote:
> What is the reason you would like to do this just for vmdk? Is it to
> avoid increasing the size of all the images when it is only vmdk you
> care about? That would makes sense.

Yes, that's it exactly. I have an existing build system in place
(which is all based on custom scripts) that I would like to upgrade to
Yocto. Our target device uses a 2GB CF card. My build system generates
an "image" which I use in conjunction with a script to create CF cards
based on any given build. There's no reason the "image" needs to be
2GB in size; the script formats and mounts the CF card, mounts the
"image", then copies the files from the image to the CF card. The
script also takes care of running LILO against the CF so it can boot.
The build system also generates a VDI (which is very much like a VMDK)
of the device which can be used for testing or development of
non-hardware-related features (e.g. web interface, snmp, etc). What I
like about the VDI is that it will start at, roughly, 200MB (which
makes it easier to copy around, download, etc) but when run will act
like the real 2GB system.

> Perhaps, for now, you could limit
> the image types you build to just vmdk and increate the size without the
> override?

Yes, that'll do for now. But I'd like to keep investigating so that
the ext3 image can be only as big as it needs to be while the
V{DI,MDK} can be dynamically sized to whatever is specified in
IMAGE_ROOTFS_SIZE_vmdk.