From: "Belal, Awais" <Awais_Belal@mentor.com>
To: "Reyna, David" <david.reyna@windriver.com>,
"bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Subject: Re: [sumo][PATCH] toaster: localhostbecontroller: fix bitbake path resolution
Date: Thu, 27 Sep 2018 07:54:10 +0000 [thread overview]
Message-ID: <1538034849901.46023@mentor.com> (raw)
In-Reply-To: <1537430385445.98207@mentor.com>
[-- Attachment #1: Type: text/plain, Size: 3200 bytes --]
>> I recommend this for both Sumo and for master as well, so that they stay in sync.
Any thoughts here?
BR,
Awais
________________________________
From: bitbake-devel-bounces@lists.openembedded.org <bitbake-devel-bounces@lists.openembedded.org> on behalf of Belal, Awais
Sent: Thursday, September 20, 2018 12:59 PM
To: Reyna, David; bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel] [sumo][PATCH] toaster: localhostbecontroller: fix bitbake path resolution
ping!
BR,
Awais
________________________________
From: Reyna, David <david.reyna@windriver.com>
Sent: Friday, September 14, 2018 12:18 PM
To: Belal, Awais; bitbake-devel@lists.openembedded.org
Cc: akuster (akuster@mvista.com)
Subject: RE: [bitbake-devel] [sumo][PATCH] toaster: localhostbecontroller: fix bitbake path resolution
Hi all,
I recommend this for both Sumo and for master as well, so that they stay in sync.
The cherry-pick should be clean between the two branches.
- David
From: bitbake-devel-bounces@lists.openembedded.org [mailto:bitbake-devel-bounces@lists.openembedded.org] On Behalf Of Belal, Awais
Sent: Thursday, September 13, 2018 2:36 AM
To: bitbake-devel@lists.openembedded.org
Subject: [bitbake-devel] [sumo][PATCH] toaster: localhostbecontroller: fix bitbake path resolution
From b736703a9d3f3c33e2e83ecd5e61dbddd5793cc8 Mon Sep 17 00:00:00 2001
From: Awais Belal <awais_belal@mentor.com>
Date: Thu, 13 Sep 2018 14:12:18 +0500
Subject: [sumo][PATCH] toaster: localhostbecontroller: fix bitbake path resolution
15340edce23e63b060c75114d508e1f76757239c introduced a way which
allowed bitbake to be found from the PATH variable when directory
structures different from poky are used. This just drops a leftover
which made the earlier implementation meaningless by reassigning
the path relative to oe-core/meta.
Signed-off-by: Awais Belal <awais_belal@mentor.com>
---
lib/toaster/bldcontrol/localhostbecontroller.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/toaster/bldcontrol/localhostbecontroller.py b/lib/toaster/bldcontrol/localhostbecontroller.py
index 3850334..63b4187 100644
--- a/lib/toaster/bldcontrol/localhostbecontroller.py
+++ b/lib/toaster/bldcontrol/localhostbecontroller.py
@@ -360,12 +360,12 @@ class LocalhostBEController(BuildEnvironmentController):
for path in os.environ["PATH"].split(os.pathsep):
if os.path.exists(os.path.join(path, 'bitbake')):
bitbake = os.path.join(path, 'bitbake')
+ logger.info("Found Bitbake at: %s" % path)
break
else:
logger.error("Looks like Bitbake is not available, please fix your environment")
# run bitbake server from the clone
- bitbake = os.path.join(self.pokydirname, 'bitbake', 'bin', 'bitbake')
toasterlayers = os.path.join(builddir,"conf/toaster-bblayers.conf")
self._shellcmd('%s bash -c \"source %s %s; BITBAKE_UI="knotty" %s --read %s --read %s '
'--server-only -B 0.0.0.0:0\"' % (env_clean, oe_init,
--
2.7.4
BR,
Awais
[-- Attachment #2: Type: text/html, Size: 9598 bytes --]
next prev parent reply other threads:[~2018-09-27 7:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 9:35 [sumo][PATCH] toaster: localhostbecontroller: fix bitbake path resolution Belal, Awais
2018-09-14 7:18 ` Reyna, David
2018-09-20 7:59 ` Belal, Awais
2018-09-27 7:54 ` Belal, Awais [this message]
2018-09-27 16:53 ` Richard Purdie
2018-09-28 7:37 ` Belal, Awais
2018-09-28 7:52 ` richard.purdie
2018-09-28 10:38 ` Belal, Awais
2018-09-28 16:08 ` akuster808
2018-09-30 7:06 ` Reyna, David
2018-09-30 7:40 ` Reyna, David
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=1538034849901.46023@mentor.com \
--to=awais_belal@mentor.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=david.reyna@windriver.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox