Thanks, the OE_TERMINALvariable did it for me
You cannot access d if you mean that
I don't mean d the object but the variables that are accessed by
d.getVar method.
all the variables are exported to the shell.
What variables exactly? I just tried to echo some of the machine config
and recipe variables and they don't exist inside the devshell
On 07/23/2018 06:05 PM, Rudolf J Streif wrote:
You can use the variable OE_TERMINAL to choose your preferred terminal.
By default it's set to auto and Bitbake figures out what terminal is
available on your system. Please refer to the manual at:
https://www.yoctoproject.org/docs/2.5/mega-manual/mega-manual.html#var-OE_TERMINAL.
Also, is it possible to access bitbake datastore from inside the
devshell(or devpyshell) ?
You cannot access d if you mean that, however, all the variables are
exported to the shell.
:rjs
On 07/23/2018 02:49 AM, MOHAMMAD RASIM wrote:
Hi,
when running bitbake with a recipe and giving the devshell as a
command bitbake runs the devshell inside xterm, on my other machine it
runs tmux.
looking at the openembedded source code here
https://github.com/openembedded/openembedded-core/blob/master/meta/lib/oe/terminal.py
I can see there are multiple classes for terminals that bitbake loop
through, but how can I tell bitbake that I prefer a certain terminal?
Also, is it possible to access bitbake datastore from inside the
devshell(or devpyshell) ?
Regards
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
