7733 2015-05-08 13:17:06 +0000 Add an option to execute task for target and all of its dependent targets 2017-03-21 01:03:44 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake 1.7 x86 Multiple RESOLVED FIXED Low enhancement Future 1 bluelightning bluelightning msm-oss poky.bs.watcher poky.watcher richard.purdie ross.burton --- --- Yes (doc changes required) oldest_to_newest 50877 0 bluelightning 2015-05-08 13:17:06 +0000 OE defines a "do_fetchall" task so you can run bitbake -c fetchall <target> and do_fetch will be run for the specified target and all of its dependent targets. However, it would be useful if we could have this mechanism in generic form so you could use it with any task. Furthermore, we'd want to ensure that -f worked with this option so you could force the task to run for targets where it's already run - one use case would be forcing do_package_qa to re-run for all dependent recipes. 71115 1 richard.purdie 2017-03-07 22:44:59 +0000 Note that this isn't just "all dependent recipes", to make this work, we actually have to traverse up the dependency tree and then back down it. For example, "bitbake core-image-sato -c fetch" but when we want a "fetchall" task, we have to look at core-image-sato:do_build, then look for all fetch tasks that are in the dependency tree for do_build. 71116 2 bluelightning 2017-03-07 23:00:33 +0000 (In reply to comment #1) > Note that this isn't just "all dependent recipes", to make this work, we > actually have to traverse up the dependency tree and then back down it. > > For example, "bitbake core-image-sato -c fetch" but when we want a > "fetchall" task, we have to look at core-image-sato:do_build, then look for > all fetch tasks that are in the dependency tree for do_build. Good point - although I'd envisaged that for this mode you would invoke bitbake without specifying a target task and specify the "run all" task separately, so that the default do_build would be the target task. e.g. bitbake --runall do_fetch core-image-minimal 71117 3 richard.purdie 2017-03-07 23:02:52 +0000 (In reply to comment #2) > (In reply to comment #1) > > Note that this isn't just "all dependent recipes", to make this work, we > > actually have to traverse up the dependency tree and then back down it. > > > > For example, "bitbake core-image-sato -c fetch" but when we want a > > "fetchall" task, we have to look at core-image-sato:do_build, then look for > > all fetch tasks that are in the dependency tree for do_build. > > Good point - although I'd envisaged that for this mode you would invoke > bitbake without specifying a target task and specify the "run all" task > separately, so that the default do_build would be the target task. e.g. > > bitbake --runall do_fetch core-image-minimal Right, this is why we end up with the do_fetchall[recideptask] = "do_${BB_DEFAULT_TASK}" style lines. I just wanted to be clear about how this would need to work for anyone who hasn't gone into the details of how this needs to work before. 71120 4 msm-oss 2017-03-08 03:00:16 +0000 https://patchwork.openembedded.org/patch/137877/ The above seems to solve the issues. 71493 5 bluelightning 2017-03-20 22:58:28 +0000 Merged to master: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=404f2aef94f8db6e46101e4ec9a6aa7e85b97880 Thanks Matthew!