From: "Denys Dmytriyenko" <denis@denix.org>
To: Chandana kalluri <ckalluri@xilinx.com>
Cc: Alejandro Hernandez Samaniego <alhe@linux.microsoft.com>,
Alexander Kanavin <alex.kanavin@gmail.com>,
OpenEmbedded Devel List
<openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] [meta-browser][PATCH] chromium.inc: Use python3native.bbclass instead of pythonnative.bbclass
Date: Mon, 22 Jun 2020 19:18:17 -0400 [thread overview]
Message-ID: <20200622231817.GK17660@denix.org> (raw)
In-Reply-To: <BYAPR02MB5926B4D4B776B27284BD4C3AB0970@BYAPR02MB5926.namprd02.prod.outlook.com>
On Mon, Jun 22, 2020 at 10:53:09PM +0000, Chandana kalluri wrote:
> I am building the meta-browser layer against poky/master and currently I am
> seeing parse errors as pythonnative and setuptools classes are no longer
> supported. Hence the patch.
So, have you had any successful builds of chromium after your patches?
> How are everyone else building python2 chromium against poky/master which
> doesn’t have support for python2 recipes/classes anymore?
You need meta-python2 layer to enable Python2 support.
> Thanks,
> Chandana
>
>
> From: Alejandro Hernandez Samaniego <alhe@linux.microsoft.com>
> Sent: Monday, June 22, 2020 3:42 PM
> To: Denys Dmytriyenko <denis@denix.org>; Alexander Kanavin <alex.kanavin@gmail.com>
> Cc: Chandana Kalluri <ckalluri@xilinx.com>; OpenEmbedded Devel List <openembedded-devel@lists.openembedded.org>; Chandana Kalluri <ckalluri@xilinx.com>
> Subject: Re: [oe] [meta-browser][PATCH] chromium.inc: Use python3native.bbclass instead of pythonnative.bbclass
>
>
> Some of it is already ported, but it doesn't look like it will be fixed soon, its easier to depend on python-native but that creates a dependency on meta-python as well as it uses EOL code.
>
> If you do that you have to manually patch lots of stuff on the v8 engine (and other components) which try calling /usr/bin/python specifically, but it will work.
>
> Alejandro
> On 6/22/20 3:32 PM, Denys Dmytriyenko wrote:
>
> Yeah, not gonna work - many people are waiting for this to happen, but alas:
>
>
>
> https://bugs.chromium.org/p/chromium/issues/detail?id=942720
>
>
>
>
>
> On Tue, Jun 23, 2020 at 12:16:51AM +0200, Alexander Kanavin wrote:
>
> Wait, did you actually test this? Chromium is not yet ready for python3,
>
> and builds will fail.
>
>
>
> Alex
>
>
>
> On Tue, 23 Jun 2020 at 00:09, Chandana kalluri <ckalluri@xilinx.com><mailto:ckalluri@xilinx.com> wrote:
>
>
>
> From dunfell onwards, python2 recipes and classes are not supported.
>
> Inherit
>
> python3native.bbclass for chromium instead of pythonnative.bbclass
>
>
>
> Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com><mailto:chandana.kalluri@xilinx.com>
>
> ---
>
> recipes-browser/chromium/chromium.inc | 2 +-
>
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
>
> diff --git a/recipes-browser/chromium/chromium.inc
>
> b/recipes-browser/chromium/chromium.inc
>
> index 14d762f..a483ec4 100644
>
> --- a/recipes-browser/chromium/chromium.inc
>
> +++ b/recipes-browser/chromium/chromium.inc
>
> @@ -18,7 +18,7 @@ TOOLCHAIN = "clang"
>
> # to build the native recipes (e.g. GN) with clang too.
>
> TOOLCHAIN_class-native = "clang"
>
>
>
> -inherit pythonnative setuptools
>
> +inherit python3native setuptools
>
>
>
> # Chromium itself is licensed under the 3-clause BSD license. However, it
>
> # depends upon several other projects whose copyright files are listed in
>
> --
>
> 2.7.4
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
next prev parent reply other threads:[~2020-06-22 23:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 22:09 [meta-browser][PATCH] chromium.inc: Use python3native.bbclass instead of pythonnative.bbclass Chandana kalluri
2020-06-22 22:16 ` [oe] " Alexander Kanavin
2020-06-22 22:32 ` Denys Dmytriyenko
2020-06-22 22:41 ` Alejandro Hernandez
2020-06-22 22:53 ` Chandana kalluri
2020-06-22 23:18 ` Denys Dmytriyenko [this message]
2020-06-23 0:16 ` Chandana kalluri
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=20200622231817.GK17660@denix.org \
--to=denis@denix.org \
--cc=alex.kanavin@gmail.com \
--cc=alhe@linux.microsoft.com \
--cc=ckalluri@xilinx.com \
--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.