]> code.ossystems Code Review - openembedded-core.git/commit
Rework how the devshell functions
authorChris Larson <chris_larson@mentor.com>
Tue, 29 Mar 2011 19:53:19 +0000 (12:53 -0700)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Wed, 10 Aug 2011 12:25:11 +0000 (13:25 +0100)
commit69f77f80965fa06a057837f8f49eda06855c4086
tree78bb7b633b22a16d2fa4e63b1c4c4dd6dcc6dd4e
parentfa7fbc9695829f7fa981b16d9559e9e984494e09
Rework how the devshell functions

In the new implementation, each known terminal is defined as a class in
oe.terminal, as a subclass of bb.process.Popen.  terminal.bbclass wraps this
functionality, providing the metadata pieces.  It obeys the OE_TERMINAL
variable, which is a 'choice' typed variable.  This variable may be 'auto',
'none', or any of the names of the defined terminals.

When using 'auto', or requesting an unsupported terminal, we attempt to spawn
them in priority order until we get one that's available on this system (and
in the case of the X terminals, has DISPLAY defined).  The 'none' value is
used when we're doing things like automated builds, and want to ensure that no
terminal is *ever* spawned, under any circumstances.

Current available terminals:

    gnome
    konsole
    xterm
    rxvt
    screen

Signed-off-by: Chris Larson <chris_larson@mentor.com>
meta/classes/devshell.bbclass
meta/classes/terminal.bbclass [new file with mode: 0644]
meta/lib/oe/terminal.py [new file with mode: 0644]