ref-manual: variables: update examples refering to DEPLOY_DIR_IMAGE

DEPLOY_DIR_IMAGE has been replaced by IMGDEPLOYDIR for most use cases
since OE-Core rev 6d969bacc718e21a5246d4da9bf9639dcae29b02. Update
examples given in the documentation to use IMGDEPLOYDIR and match their
implementation.

(From yocto-docs rev: 6cad5984306ffbf748a888cedc1a5015105e89fa)

Signed-off-by: Daniel Wagenknecht <dwagenknecht@emlix.com>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Reviewed-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Daniel Wagenknecht 2021-06-11 08:26:12 +02:00 committed by Richard Purdie
parent 5f978a6cca
commit f5e157d229

View File

@ -2946,7 +2946,7 @@ system and gives an overview of their function and contents.
an override for the associated type. Here is an example::
IMAGE_CMD_jffs2 = "mkfs.jffs2 --root=${IMAGE_ROOTFS} \
--faketime --output=${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.jffs2 \
--faketime --output=${IMGDEPLOYDIR}/${IMAGE_NAME}.rootfs.jffs2 \
${EXTRA_IMAGECMD}"
You typically do not need to set this variable unless you are adding
@ -3095,10 +3095,10 @@ system and gives an overview of their function and contents.
The :ref:`image <ref-classes-image>` class defines the manifest
file as follows::
IMAGE_MANIFEST ="${DEPLOY_DIR_IMAGE}/${IMAGE_NAME}.rootfs.manifest"
IMAGE_MANIFEST ="${IMGDEPLOYDIR}/${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.manifest"
The location is
derived using the :term:`DEPLOY_DIR_IMAGE`
derived using the :term:`IMGDEPLOYDIR`
and :term:`IMAGE_NAME` variables. You can find
information on how the image is created in the ":ref:`overview-manual/concepts:image generation`"
section in the Yocto Project Overview and Concepts Manual.