This recipe is not an image recipe. It is a recipe that packages up our image for deployment/updates in the field. Your method assumes I am editing the image recipe.
On Wed, Nov 22, 2017 at 4:01 AM, Martin Hundebøll <[email protected]> wrote: > Hi Paul, > > On 2017-11-22 09:10, Paul Knopf wrote: > >> I have a recipe that depends on a deployed output from an image. >> >> ---------------------------------------------------------- >> SRC_URI += "file://${DEPLOY_DIR_IMAGE}/my-image-${MACHINE}.wic.update. >> tar.gz;subdir=update" >> do_fetch[depends] += "my-image:do_build" >> ---------------------------------------------------------- >> >> Will the hash for "do_fetch" be computed after "my-image:do_build" is >> executed? >> > > The "dependency" hash is based on the hash of the my-image recipe, so that > if you change the my-image.bb, then the hash of your dependent recipe > changes too. > > If not, how would you propose I do something like this? >> > > Don't put deployed images in SRC_URI, and don't put task dependencies in > do_fetch, as that messes with do_fetchall, should you ever need to run that. > > Look at what other recipes are doing when using images from > DEPLOY_DIR_IMAGE. A reworked example from one of our recipes: > > do_image[depends] += "my-image:do_image_complete" > > IMAGE_PREPROCESS_COMMAND += "image_prepare" > image_prepare() { > install ${DEPLOY_DIR_IMAGE}/my-image-${MACHINE}.wic.update.tar.gz > ${IMAGE_ROOTFS}/ > } > > > I hope that helps! > > // Martin >
-- _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
