From: Rudolf J Streif <rudolf.streif@gmail.com>
To: MOHAMMAD RASIM <mohammad.rasim96@gmail.com>, yocto@yoctoproject.org
Subject: Re: How to tell bitbake my prefered terminal in for devshell and access bitbake datastore?
Date: Mon, 23 Jul 2018 08:05:53 -0700 [thread overview]
Message-ID: <fa1281bd-1bb1-7126-d142-1ca4e599794a@gmail.com> (raw)
In-Reply-To: <1e741f3f-f20e-4e38-d9ec-643e22b34e2d@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1136 bytes --]
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
>
--
Rudolf J Streif
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 499 bytes --]
next prev parent reply other threads:[~2018-07-23 15:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 9:49 How to tell bitbake my prefered terminal in for devshell and access bitbake datastore? MOHAMMAD RASIM
2018-07-23 15:05 ` Rudolf J Streif [this message]
2018-07-23 15:37 ` MOHAMMAD RASIM
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa1281bd-1bb1-7126-d142-1ca4e599794a@gmail.com \
--to=rudolf.streif@gmail.com \
--cc=mohammad.rasim96@gmail.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.