[OE-core] [PATCH] Add support for running custom terminals.

Example config: OE_TERMINAL = "custom" OE_TERMINAL_CUSTOMCMD = "mysuperterm" Signed-off-by: Morten Minde Neergaard --- meta/classes/terminal.bbclass | 10 ++ meta/lib/oe/terminal.py | 17 - 2 files changed, 22 insertions(+), 5 deletions(-

[OE-core] [PATCH] Add support for running custom terminals. Example config: OE_TERMINAL = "custom" / OE_TERMINAL_CUSTOMCMD = "myterm"

Signed-off-by: Morten Minde Neergaard --- meta/classes/terminal.bbclass |6 +++--- meta/lib/oe/terminal.py | 41 - 2 files changed, 31 insertions(+), 16 deletions(-) diff --git a/meta/classes/terminal.bbclass b/meta/classes/terminal.bbclass

Re: [OE-core] Only one copy of bitbake should be run against a build directory

from the bitbake. So, my setup is: patch plus bitbake running in a screen instance plus these settings: OE_TERMINAL = "custom" OE_TERMINAL_CUSTOMCMD = "screen" OE_TERMINAL_EXPORTS += "STY" (Should I submit this (non-obtrusive) patch som

Re: [OE-core] Customize devshell terminal command / environment?

At 09:44, Mon 2012-09-24, Morten Minde Neergaard wrote: […] > * Make a new CustomTerminal terminal class that takes its command line >from a configuration directive, e.g. OE_TERMINAL_CUSTOMCMD > * Allowing option overrides for each of the existing classes > * Detect the STY

[OE-core] Customize devshell terminal command / environment?

D * Allowing option overrides for each of the existing classes * Detect the STY variable if present, and use the existing screen if one exists I'm strongly in favour of implementing the first one. Any objections or interjections? =) -