From: Tim Orling <timothy.t.orling@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/4] scons.bbclass: use python3-scons
Date: Fri, 7 Jun 2019 16:47:52 -0700 [thread overview]
Message-ID: <0f5adba2f96da9396faa1e70f9eed84118cf735e.1559950879.git.timothy.t.orling@linux.intel.com> (raw)
In-Reply-To: <cover.1559950879.git.timothy.t.orling@linux.intel.com>
SCons has supported python3 since 3.0.0 release, use it.
[YOCTO #13381]
Signed-off-by: Tim Orling <timothy.t.orling@linux.intel.com>
---
meta/classes/scons.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/scons.bbclass b/meta/classes/scons.bbclass
index 9ee7d1587d..a8ddae35f7 100644
--- a/meta/classes/scons.bbclass
+++ b/meta/classes/scons.bbclass
@@ -1,4 +1,4 @@
-DEPENDS += "python-scons-native"
+DEPENDS += "python3-scons-native"
EXTRA_OESCONS ?= ""
--
2.20.1
next prev parent reply other threads:[~2019-06-07 23:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 23:47 [PATCH 0/4] Move SCons to Python 3 Tim Orling
2019-06-07 23:47 ` [PATCH 1/4] python3-scons-{native}: add recipe for v3.0.5 Tim Orling
2019-06-08 0:56 ` Tim Orling
2019-06-07 23:47 ` Tim Orling [this message]
2019-06-20 13:36 ` [PATCH 2/4] scons.bbclass: use python3-scons Khem Raj
2019-06-21 0:18 ` Tim Orling
2019-06-21 3:27 ` Khem Raj
2019-06-22 8:58 ` Adrian Bunk
2019-06-23 0:03 ` Khem Raj
2019-06-23 16:44 ` Tim Orling
2019-06-23 19:24 ` Adrian Bunk
2019-06-24 1:49 ` Tim Orling
2019-06-24 2:41 ` Alistair Francis
2019-06-24 8:20 ` Adrian Bunk
2019-06-24 17:27 ` Alistair Francis
2019-06-07 23:47 ` [PATCH 3/4] serf: switch to python3-scons-native Tim Orling
2019-06-10 5:10 ` Mittal, Anuj
2019-06-10 5:22 ` Tim Orling
2019-06-12 20:52 ` Khem Raj
2019-06-07 23:47 ` [PATCH 4/4] oeqa/runtime: add simple test for scons Tim Orling
2019-06-08 3:54 ` ✗ patchtest: failure for Move SCons to Python 3 Patchwork
2019-06-08 4:04 ` Tim Orling
2019-06-08 7:13 ` [PATCH 0/4] " Burton, Ross
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=0f5adba2f96da9396faa1e70f9eed84118cf735e.1559950879.git.timothy.t.orling@linux.intel.com \
--to=timothy.t.orling@linux.intel.com \
--cc=openembedded-core@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.