summaryrefslogtreecommitdiffstats
path: root/bitbake/bin/bitbake-dumpsig
diff options
context:
space:
mode:
authorJason Wessel <jason.wessel@windriver.com>2012-09-17 17:43:49 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2012-09-24 15:35:32 +0100
commit98ac5e4e6230095487b819b911890ec64e28d5f7 (patch)
treec25e92de41ccdeca570fb3a7b744c0b3327f2c17 /bitbake/bin/bitbake-dumpsig
parenteab93b0d625aba061a73b9c5f7ce7828495f1338 (diff)
downloadpoky-98ac5e4e6230095487b819b911890ec64e28d5f7.tar.gz
bitbake: event.py, knotty.py, ncurses.py, runningbuild.py: Add support for LogExecTTY event
The LogExecTTY even is intended to provide the ability to spawn a task on a the controlling tty, if a tty is availble. When a controlling tty is not availble the previous behavior is preserved where a warning is issued about the action an end user must execute. All the available UI's were tested against the new event type. This feature is primarily intended for hooking up a screen client session automatically on the controlling tty to allow for a more streamlined end user experience when using a pure command line driven environment. The changes that send the LogExecTTY event are in the oe-core side. (Bitbake rev: cffe80d82a46aaf52ff4a7b6409435754043553f) Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/bin/bitbake-dumpsig')
0 files changed, 0 insertions, 0 deletions