Thanks! You are right, the do_deploy_append installs the
image_signed.fit in the ${DEPLOY_DIR_IMAGE}(I should have kept that line
in the previous mail also):
do_deploy_append() {
[...]
#this line creates the image_signed.fit file
mkimage [...] image_signed.fit
install -m 0644 image_signed.fit ${DEPLOY_DIR_IMAGE}/.
[...]
}
The doc mentions in regards to DEPLOYDIR:
"Recipes inheriting the |deploy| class should copy files to be deployed
into |DEPLOYDIR|, and the class will take care of copying them into
|DEPLOY_DIR_IMAGE|
<http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-DEPLOY_DIR_IMAGE>
afterwards."
So I should just replace ${DEPLOY_DIR_IMAGE} with ${DEPLOYDIR} and I get
the same behaviour as before + the benefit of sstate cache ?
Thanks
On 09/03/17 09:22, Patrick Ohly wrote:
On Thu, 2017-03-09 at 08:54 +0200, Mircea Gliga wrote:
Long story short: I have problems building an image, in a clean build
directory, reusing the shared state cache and downloads from a previous
build.
A file created in the do_deploy_append task is not created(restored)
anymore when building using a previous sstate.
And now the long description:
In my custom layer, in a kernel recipe, linux-stable.bb, I have appended
some operations to the `deploy` task, one of them is creating an U-Boot
FIT image:
linux-stable.bb:
do_deploy_append() {
[...]
#this line creates the image_signed.fit file
mkimage [...] image_signed.fit
[...]
}
Are you writing image_signed.fit into the ${DEPLOYDIR} or
${DEPLOY_DIR_IMAGE}? When writing directly into ${DEPLOY_DIR_IMAGE}, you
bypass the mechanism which adds files to the sstate cache and then you
get exactly the problem you describe.
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
