diff options
author | Paul Eggleton <paul.eggleton@linux.intel.com> | 2016-12-16 07:09:13 +1300 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-12-20 15:22:50 +0000 |
commit | fe7e75075e2d55a45ad2b81c9e493068a156d1dc (patch) | |
tree | d5dddcd32bb50c0cc70fa40120a0acf2f63d859f /meta/recipes-connectivity | |
parent | 764a7801361c6f57ff366be641b1410e7b36f56b (diff) | |
download | poky-fe7e75075e2d55a45ad2b81c9e493068a156d1dc.tar.gz |
bitbake: runqueue: dry-run real tasks when BB_SETSCENE_ENFORCE is set
For the purposes BB_SETSCENE_ENFORCE is designed for (in OE, it is used
by the installation process for the extensible SDK), we don't actually
need the whitelisted real tasks to execute - we just need to have them
in the dependency tree so that we get all of the setscene tasks they
depend on to run. Therefore we can actually dry-run those real tasks
i.e. they won't be run (and thus we won't waste a significant amount of
time doing so) and won't be stamped as having run either. We do already
have a dry-run mode in BitBake (activated by the -n or --dry-run command
line option), but it dry-runs the setscene tasks as well which we don't
want here.
Note that this has no effect on the checking we are doing with
BB_SETSCENE_ENFORCE to ensure that only whitelisted real tasks are
scheduled to run - that's handled separately.
Fixes [YOCTO #10369].
(Bitbake rev: 58f084291beb3a87d8d9fdb36dfe7eff911fa36b)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-connectivity')
0 files changed, 0 insertions, 0 deletions