diff options
author | Patrick Ohly <patrick.ohly@intel.com> | 2015-09-24 16:53:10 +0200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-09-28 11:58:22 +0100 |
commit | e3ff509091cbbfdef851f8a3c9e31c7b76d37e89 (patch) | |
tree | 09d9085c7d7c72832c4afee4eab2240ef33ff73a /meta/classes/image-vm.bbclass | |
parent | 55e8067d3fb6a1fc97b4486e28e3e3bae2b5cd00 (diff) | |
download | openembedded-core-e3ff509091cbbfdef851f8a3c9e31c7b76d37e89.tar.gz openembedded-core-e3ff509091cbbfdef851f8a3c9e31c7b76d37e89.tar.bz2 openembedded-core-e3ff509091cbbfdef851f8a3c9e31c7b76d37e89.zip |
image types: add hdddirect
When image-vm.bbclass was introduced, it indirectly also introduced a
".hdddirect" image type based on boot-directdisk.bbclass. However, one
could only get that image when also enabling at least one of the
virtual machine images.
The .hdddirect images are useful by themselves. By registering
image-vm.bbclass as implementation of it, it becomes possible to
select them with:
IMAGE_FSTYPES = "hdddirect"
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'meta/classes/image-vm.bbclass')
-rw-r--r-- | meta/classes/image-vm.bbclass | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/meta/classes/image-vm.bbclass b/meta/classes/image-vm.bbclass index 0632667084..5ddd1cb274 100644 --- a/meta/classes/image-vm.bbclass +++ b/meta/classes/image-vm.bbclass @@ -18,7 +18,8 @@ inherit boot-directdisk IMAGE_TYPEDEP_vmdk = "ext4" IMAGE_TYPEDEP_vdi = "ext4" IMAGE_TYPEDEP_qcow2 = "ext4" -IMAGE_TYPES_MASKED += "vmdk vdi qcow2" +IMAGE_TYPEDEP_hdddirect = "ext4" +IMAGE_TYPES_MASKED += "vmdk vdi qcow2 hdddirect" create_vmdk_image () { qemu-img convert -O vmdk ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.hdddirect ${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.vmdk |