From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: akuster808 <akuster808@gmail.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
OpenEmbedded Devel List
<openembedded-devel@lists.openembedded.org>
Subject: Re: [OE-core] devshell not working after pulling latest oe-core changes
Date: Mon, 13 Mar 2017 07:19:49 +0000 [thread overview]
Message-ID: <1489389589.13980.25.camel@linuxfoundation.org> (raw)
In-Reply-To: <53aa1073-01e3-8315-cac6-ad0197a2d6c8@gmail.com>
On Mon, 2017-03-13 at 00:09 -0700, akuster808 wrote:
> tmux split-window "do_terminal"
> tmux new-window -n "OpenEmbedded Developer Shell" "do_terminal"
> terminology -T="OpenEmbedded Developer Shell" -e do_terminal
> gnome-terminal -t "OpenEmbedded Developer Shell" -x do_terminal
> mate-terminal -t "OpenEmbedded Developer Shell" -x do_terminal
> konsole --separate --workdir . -p tabtitle="OpenEmbedded
> Developer
> Shell" -e do_terminal
> xfce4-terminal -T "OpenEmbedded Developer Shell" -e
> "do_terminal"
> xterm -T "OpenEmbedded Developer Shell" -e do_terminal
> rxvt -T "OpenEmbedded Developer Shell" -e do_terminal
> tmux new -d -s devshell -n devshell "do_terminal"
> screen -D -m
I suspect we need a:
HOSTTOOLS_NONFATAL += "xterm rxvt tmux screen xfce4-terminal mate-
terminal konsole terminology gnome-terminal"
into terminal.bbclass.
Cheers,
Richard
WARNING: multiple messages have this Message-ID (diff)
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: akuster808 <akuster808@gmail.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
OpenEmbedded Devel List
<openembedded-devel@lists.openembedded.org>
Subject: Re: devshell not working after pulling latest oe-core changes
Date: Mon, 13 Mar 2017 07:19:49 +0000 [thread overview]
Message-ID: <1489389589.13980.25.camel@linuxfoundation.org> (raw)
In-Reply-To: <53aa1073-01e3-8315-cac6-ad0197a2d6c8@gmail.com>
On Mon, 2017-03-13 at 00:09 -0700, akuster808 wrote:
> tmux split-window "do_terminal"
> tmux new-window -n "OpenEmbedded Developer Shell" "do_terminal"
> terminology -T="OpenEmbedded Developer Shell" -e do_terminal
> gnome-terminal -t "OpenEmbedded Developer Shell" -x do_terminal
> mate-terminal -t "OpenEmbedded Developer Shell" -x do_terminal
> konsole --separate --workdir . -p tabtitle="OpenEmbedded
> Developer
> Shell" -e do_terminal
> xfce4-terminal -T "OpenEmbedded Developer Shell" -e
> "do_terminal"
> xterm -T "OpenEmbedded Developer Shell" -e do_terminal
> rxvt -T "OpenEmbedded Developer Shell" -e do_terminal
> tmux new -d -s devshell -n devshell "do_terminal"
> screen -D -m
I suspect we need a:
HOSTTOOLS_NONFATAL += "xterm rxvt tmux screen xfce4-terminal mate-
terminal konsole terminology gnome-terminal"
into terminal.bbclass.
Cheers,
Richard
next prev parent reply other threads:[~2017-03-13 7:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 7:09 devshell not working after pulling latest oe-core changes akuster808
2017-03-13 7:19 ` Richard Purdie [this message]
2017-03-13 7:19 ` Richard Purdie
2017-03-13 7:37 ` [OE-core] " akuster808
2017-03-13 7:37 ` akuster808
2017-03-13 7:42 ` [OE-core] " Robert Yang
2017-03-13 7:42 ` Robert Yang
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=1489389589.13980.25.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=akuster808@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.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.