On 04-04-17 15:54, André Draszik wrote:
Hi,
Is it possible to invalidate one recipe's hash for a specific task from
another recipe?
I hope not...
More specifically, I have an initramfs image recipe and a main image recipe
where do_rootfs of the main image [depends] on do_deploy of initramfs.
If do_rootfs of the main image needs to be re-run, I need to make sure that
do_rootfs of the initramfs image is re-run (and of course do_deploy) before.
Basically I want to add a timestamp to both images, and the timestamp should
be the same.
Using my current dependencies, do_rootfs of the main image is re-run if the
initramfs is re-deployed:
--- snip main_image.bb: ---
do_rootfs[depends] += "initramfs:do_deploy"
--- snap ---
but I need this both ways. Just adding the equivalent to the initramfs
recipe results in bitbake complaining about a recursive dependency loop.
Can this be achieved? Even some pointers would be helpful...
Or some other approach where I can add the same timestamp to both images if
either of the images needed to be rebuilt due to some change?
What I did was have two image recipes, let's say "big-image" and
"small-image". The big-image included a package called "big-project". To the
"big-project.bb" recipe I added:
DEPENDS += "small-image"
do_install[depends] += "small-image:do_image_complete"
And in the do_install I copy the stuff from small-image into whereever I
wanted it to be insided the small image.
Maybe this covers your use case?
Kind regards,
Mike Looijmans
System Expert
TOPIC Products
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijm...@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
