From: Ming Liu <ming....@toradex.com> The results in ${IMGDEPLOYDIR} generated by a image task could be used by later image tasks, hence they should be excluded by rm_work. Or else when a image task gets rerun but one of its dependent image task does not, then the results generated by this dependent image task would not be there in ${IMGDEPLOYDIR}.
Signed-off-by: Ming Liu <ming....@toradex.com> --- meta/classes/image.bbclass | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass index 682858d..d16e285 100644 --- a/meta/classes/image.bbclass +++ b/meta/classes/image.bbclass @@ -84,6 +84,10 @@ PACKAGE_INSTALL_ATTEMPTONLY ?= "${FEATURE_INSTALL_OPTIONAL}" IMGDEPLOYDIR = "${WORKDIR}/deploy-${PN}-image-complete" +# The results in ${IMGDEPLOYDIR} generated by a image task could be used by +# later image tasks, hence they should be excluded by rm_work. +RM_WORK_EXCLUDE_ITEMS += "deploy-${PN}-image-complete" + # Images are generally built explicitly, do not need to be part of world. EXCLUDE_FROM_WORLD = "1" -- 2.7.4 -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core