openembedded-core.git/meta/classes/image.bbclass, branch morty

Remove RM_OLD_IMAGE, it's no longer useful

2016-10-15T08:48:28+00:00

Since the move to put image deployment under sstate control in
d54339d4b1a7e884de636f6325ca60409ebd95ff old images are automatically
removed before a new image is deployed (the default behaviour of the
sstate logic).

RM_OLD_IMAGE is therefore no longer required to provide this
behaviour, remove the variable and its users.

Signed-off-by: Joshua Lock 
Signed-off-by: Ross Burton

image.bbclass: Make do_rootfs depend on PACKAGE_EXCLUDE_COMPLEMENTARY

2016-10-05T22:22:33+00:00

Signed-off-by: Peter Kjellerstedt 
Signed-off-by: Richard Purdie

image.bbclass: add IMAGE_DEVICE_TABLE to rootfs[vardeps]

2016-09-15T11:14:40+00:00

IMAGE_DEVICE_TABLE and IMAGE_DEVICE_TABLES are both referenced by
_create_devfs, therefore ensure that rootfs is rebuilt if changes
are made to either variable.

Signed-off-by: Andre McCurdy 
Signed-off-by: Richard Purdie

image.bbclass: also mask debugfs versions of masked images

2016-09-14T21:20:04+00:00

When IMAGE_GEN_DEBUGFS is enabled, and IMAGE_FSTYPES_DEBUGFS is left
at its default (as suggested by local.conf.sample.extended),
recipe parsing fails:

bitbake kern-tools-native # or anything else for that matter
ERROR: /meta/recipes-core/images/build-appliance-image_15.0.0.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'debugfs_vmdk' - possibly invalid type name or missing support class
ERROR: Failed to parse recipe: /meta/recipes-core/images/build-appliance-image_15.0.0.bb

Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

i.e. bitbake doesn't even finish parsing...

Since IMAGE_FSTYPES_DEBUGFS is based on IMAGE_FSTYPES, and
since the build-appliance-image is setting IMAGE_FSTYPES
to vmdk, image.bbclass/image_types.bbclass will be trying
to build a debugfs_vmdk, causing the error, as this is not
implemented.

One solution to solving this problem could be as simple as
adding a line
IMAGE_FSTYPES_DEBUGFS_remove = "vmdk"
to the build-appliance-image recipe, but that is very
specific to the error encountered and carries the risk of
the error being reintroduced in another recipe.

Another solution could be to add 'debugfs_vmdk' to
IMAGE_TYPES_MASKED in image-vm.bbclass, but again, this
approach doesn't seem generic enough.

None of the live and vm type images have an implementation
for building a debugfs version, it doesn't seem to make
sense to build debugfs versions of any of them anyway, and
given IMAGE_TYPES_MASKED appears to be intended for those
image types exclusively, it seems the right approach is to
unconditionally also mask all debugfs_ flavours from
IMAGE_TYPES_MASKED to achieve a generic solution.

Do that so.

Signed-off-by: André Draszik
Signed-off-by: Ross Burton

image.bbclass: do not check size of the debugfs image

2016-09-14T21:20:04+00:00

The debugfs is supposed to be used in addition to the
normal image for debugging purposes, it doesn't make
sense to artificially limit its maximum size.

Signed-off-by: André Draszik 
Signed-off-by: Ross Burton

meta: cleanup d.getVar(var, 0)

2016-09-14T21:20:03+00:00

Signed-off-by: Robert Yang 
Signed-off-by: Ross Burton

image.bbclass: Put image_complete under sstate control

2016-09-03T23:05:12+00:00

Adding image_complete task should make sstate machinery
to generate manifest for deployed images and do final
deployment to DEPLOY_DIR_IMAGE.

Made sure IMGDEPLOYDIR doesn't contain images from past deployments
to prevent them to be included into sstate manifests.

Set stamp-extra-info flag for do_image_complete task. This flag
is used in the name of sstate manifest. Setting it to predetermined
value for image_complete should help to get correct manifest
filenames when processing runQueueTask events.

Signed-off-by: Ed Bartosh 
Signed-off-by: Richard Purdie

image: Deploy images to IMGDEPLOYDIR

2016-09-03T23:05:12+00:00

Changed deployment directory from DEPLOY_DIR_IMAGE to
IMGDEPLOYDIR to make sstate machinery to do final deployment and
generate manifest.

Renamed variable deploy_dir to deploy_dir_image in selftest code
to avoid confusion with DEPLOYDIR variable.

Updated the code of rootfs.py:Rootfs class to use IMGDEPLOYDIR variable
as it's now used as a new deployment destination.

Signed-off-by: Ed Bartosh 
Signed-off-by: Richard Purdie

image/populate_sdk_base: Add *DEPLOYDIR variables

2016-09-03T23:05:12+00:00

This is a preparation for changing deployment directory for image
and populate_sdk targets.

Introduced new variables, IMGDEPLOYDIR and SDKDEPLOYDIR. Set it to current
image/sdk deployment locations.

Signed-off-by: Ed Bartosh 
Signed-off-by: Richard Purdie

image.bbclass: rename COMPRESS(ION) to CONVERSION

2016-08-18T08:27:14+00:00

With the enhanced functionality, the term "compression" is no longer
accurate, because the mechanism also gets used for conversion
operations that do not actually compress data.

It is possible to remove this naming problem in a backward-compatible
manner by including COMPRESSIONTYPES in CONVERSIONTYPES and checking for
the old COMPRESS_CMD/DEPENDS as fallbacks.

[YOCTO #9346]

Signed-off-by: Patrick Ohly 
Signed-off-by: Ed Bartosh 
Signed-off-by: Ross Burton