summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/bb/command.py
diff options
context:
space:
mode:
authorPaul Eggleton <paul.eggleton@linux.intel.com>2017-07-19 11:56:06 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-07-21 08:41:12 +0100
commit7eb654cb4d82b54e3e4df0a57face61063b72c45 (patch)
treef1d3e07fadfa211cfb832295847ac771aaa80d9c /bitbake/lib/bb/command.py
parente1285712fa634e2d88f263fa9aa624bdcd22b3fa (diff)
downloadpoky-7eb654cb4d82b54e3e4df0a57face61063b72c45.tar.gz
bitbake: tinfoil: add functionality for running full builds
Up to this point, if you wanted to run build tasks in the normal way they get run from a python script, there was no other way than to shell out to bitbake. Worse than that, you couldn't have tinfoil active during that because only one bitbake instance could be running at once. As long as we're prepared to handle the events produced, we can create a wrapper around calling the buildTargets command. Borrow code from knotty to do this in such a way that we get the expected running task display (courtesy of TermFilter) and Ctrl+C handling. (Bitbake rev: 43761eee756be52a1021be53a40dc591a6c35fa7) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/lib/bb/command.py')
0 files changed, 0 insertions, 0 deletions