All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tammana, Gowtham" <g-tammana@ti.com>
To: Denys Dmytriyenko <denis@denix.org>
Cc: "meta-arago@arago-project.org" <meta-arago@arago-project.org>
Subject: Re: [EXTERNAL] [oe-layersetup][PATCH] configs/arago-dunfell: more detailed template for enabling chromium
Date: Wed, 24 Mar 2021 22:44:08 +0000	[thread overview]
Message-ID: <546c64e843c24ecab92584a279fc0bde@ti.com> (raw)
In-Reply-To: <20210324194215.GQ18041@denix.org>



>-----Original Message-----
>From: Denys Dmytriyenko <denis@denix.org>
>Sent: Wednesday, March 24, 2021 2:42 PM
>To: Tammana, Gowtham <g-tammana@ti.com>
>Cc: meta-arago@arago-project.org
>Subject: Re: [EXTERNAL] [meta-arago] [oe-layersetup][PATCH] configs/arago-
>dunfell: more detailed template for enabling chromium
>
>On Wed, Mar 24, 2021 at 07:18:25PM +0000, Tammana, Gowtham wrote:
>>
>>
>> >-----Original Message-----
>> >From: meta-arago-bounces@arago-project.org <meta-arago-bounces@arago-
>> >project.org> On Behalf Of Denys Dmytriyenko
>> >Sent: Tuesday, March 23, 2021 4:16 PM
>> >To: meta-arago@arago-project.org
>> >Subject: [EXTERNAL] [meta-arago] [oe-layersetup][PATCH] configs/arago-
>> >dunfell: more detailed template for enabling chromium
>> >
>> >Disabled (commented out) by default.
>> >
>> >Signed-off-by: Denys Dmytriyenko <denis@denix.org>
>> >---
>> > configs/arago-dunfell-config.txt                  |  6 +++++-
>> > configs/arago-dunfell-next-config.txt             |  6 +++++-
>> > sample-files/bblayers-dunfell-browser.conf.sample | 12 ++++++++++++
>> > 3 files changed, 22 insertions(+), 2 deletions(-)
>> > create mode 100644 sample-files/bblayers-dunfell-browser.conf.sample
>> >
>> >diff --git a/configs/arago-dunfell-config.txt b/configs/arago-dunfell-
>> >config.txt
>> >index b45ee3e..173499b 100644
>> >--- a/configs/arago-dunfell-config.txt
>> >+++ b/configs/arago-dunfell-config.txt
>> >@@ -3,7 +3,8 @@
>> >
>> > bitbake,git://git.openembedded.org/bitbake,1.46,HEAD
>> > meta-arago,git://arago-project.org/git/meta-
>> >arago.git,dunfell,HEAD,layers=meta-arago-distro:meta-arago-extras
>> >-#meta-browser,git://github.com/OSSystems/meta-
>> >browser.git,master,5f365ef0f842ba4651efe88787cf9c63bc8b6cb3,layers=
>> >+# meta-browser,git://github.com/OSSystems/meta-
>> >browser.git,master,5f365ef0f842ba4651efe88787cf9c63bc8b6cb3,layers=
>> >+# meta-python2,git://git.openembedded.org/meta-
>> >python2,dunfell,HEAD,layers=
>>
>> I see chromium/qtwebengine python2 build related patches followed this.
>And I
>> am reading that commented layers here need to be enabled to build those
>recipes.
>> Isn't it or am I missing something else.
>>
>> Btw what's the current state of meta-python2, I recall from earlier that
>support
>> for it is being discontinued.
>
>Python2 has been EOL for over a year now, since beginning od 2020:
>https://www.python.org/doc/sunset-python-2/
>
>As of meta-python2 - it is a community-supported layer just to help people
>migrate to Python3. There's no official support for it and it is solely in
>hands of volunteers. It is not recommended to be used in new products.
>That
>is why the setup above is disabled by default.
>
>Unfortunately, Chromium (and qtwebengine uses Chromium engine) still
>depends
>on Python2 for now. The purpose of these patches is to cleanup recipes and
>provide a templaye for anyone willing to enable Chromium at own risk. 

Thanks for the clarification, understood the intent behind these changes.
I have tried something similar for building qtwebengine earlier. Thanks for
these changes.

Reviewed-by: Gowtham Tammana <g-tammana@ti.com>

>--
>Denys
>
>> Gowtham
>>
>> > meta-qt5,git://github.com/meta-qt5/meta-qt5.git,dunfell,HEAD,layers=
>> > meta-virtualization,git://git.yoctoproject.org/meta-
>> >virtualization,dunfell,HEAD,layers=
>> > meta-openembedded,git://git.openembedded.org/meta-
>> >openembedded,dunfell,HEAD,layers=meta-networking:meta-python:meta-
>oe:meta-
>> >gnome:meta-filesystems
>> >@@ -11,4 +12,7 @@ meta-ti,git://git.yoctoproject.org/meta-
>> >ti,dunfell,HEAD,layers=
>> > meta-arm,git://git.yoctoproject.org/meta-
>> >arm,dunfell,c4f04f3fb66f8f4365b08b553af8206372e90a63,layers=meta-
>arm:meta-
>> >arm-toolchain
>> > oe-core,git://git.openembedded.org/openembedded-
>> >core,dunfell,HEAD,layers=meta
>> > OECORELAYERCONF=./sample-files/bblayers.conf.sample
>> >+# if meta-browser/5f365ef0f842ba4651efe88787cf9c63bc8b6cb3 above is
>> >enabled,
>> >+# use below for OECORELAYERCONF to mark it compatible with dunfell
>> >+#OECORELAYERCONF=./sample-files/bblayers-dunfell-browser.conf.sample
>> > OECORELOCALCONF=./sample-files/local-arago64.conf.sample
>> >diff --git a/configs/arago-dunfell-next-config.txt b/configs/arago-
>dunfell-
>> >next-config.txt
>> >index 8d629c4..9f5eeb9 100644
>> >--- a/configs/arago-dunfell-next-config.txt
>> >+++ b/configs/arago-dunfell-next-config.txt
>> >@@ -3,7 +3,8 @@
>> >
>> > bitbake,git://git.openembedded.org/bitbake,1.46,HEAD
>> > meta-arago,git://arago-project.org/git/meta-arago.git,dunfell-
>> >next,HEAD,layers=meta-arago-distro:meta-arago-extras
>> >-#meta-browser,git://github.com/OSSystems/meta-
>> >browser.git,master,5f365ef0f842ba4651efe88787cf9c63bc8b6cb3,layers=
>> >+# meta-browser,git://github.com/OSSystems/meta-
>> >browser.git,master,5f365ef0f842ba4651efe88787cf9c63bc8b6cb3,layers=
>> >+# meta-python2,git://git.openembedded.org/meta-
>> >python2,dunfell,HEAD,layers=
>> > meta-qt5,git://github.com/meta-qt5/meta-qt5.git,dunfell,HEAD,layers=
>> > meta-virtualization,git://git.yoctoproject.org/meta-
>> >virtualization,dunfell,HEAD,layers=
>> > meta-openembedded,git://git.openembedded.org/meta-
>> >openembedded,dunfell,HEAD,layers=meta-networking:meta-python:meta-
>oe:meta-
>> >gnome:meta-filesystems
>> >@@ -11,4 +12,7 @@ meta-ti,git://git.yoctoproject.org/meta-ti,dunfell-
>> >next,HEAD,layers=
>> > meta-arm,git://git.yoctoproject.org/meta-
>> >arm,dunfell,c4f04f3fb66f8f4365b08b553af8206372e90a63,layers=meta-
>arm:meta-
>> >arm-toolchain
>> > oe-core,git://git.openembedded.org/openembedded-
>> >core,dunfell,HEAD,layers=meta
>> > OECORELAYERCONF=./sample-files/bblayers.conf.sample
>> >+# if meta-browser/5f365ef0f842ba4651efe88787cf9c63bc8b6cb3 above is
>> >enabled,
>> >+# use below for OECORELAYERCONF to mark it compatible with dunfell
>> >+#OECORELAYERCONF=./sample-files/bblayers-dunfell-browser.conf.sample
>> > OECORELOCALCONF=./sample-files/local-arago64.conf.sample
>> >diff --git a/sample-files/bblayers-dunfell-browser.conf.sample
>b/sample-
>> >files/bblayers-dunfell-browser.conf.sample
>> >new file mode 100644
>> >index 0000000..1e525d5
>> >--- /dev/null
>> >+++ b/sample-files/bblayers-dunfell-browser.conf.sample
>> >@@ -0,0 +1,12 @@
>> >+# This template file was created by taking the oe-
>> >core/meta/conf/bblayers.conf
>> >+# file and removing the BBLAYERS section at the end.
>> >+
>> >+# LAYER_CONF_VERSION is increased each time build/conf/bblayers.conf
>> >+# changes incompatibly
>> >+LCONF_VERSION = "6"
>> >+
>> >+BBPATH = "${TOPDIR}"
>> >+BBFILES ?= ""
>> >+
>> >+OVERRIDES = "forcevariable"
>> >+LAYERSERIES_COMPAT_browser-layer_forcevariable = "dunfell"
>> >--
>> >2.7.4
>> >
>> >_______________________________________________
>> >meta-arago mailing list
>> >meta-arago@arago-project.org
>> >http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
>>


      reply	other threads:[~2021-03-24 22:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-23 21:15 [oe-layersetup][PATCH] configs/arago-dunfell: more detailed template for enabling chromium Denys Dmytriyenko
2021-03-24 19:18 ` [EXTERNAL] " Tammana, Gowtham
2021-03-24 19:42   ` Denys Dmytriyenko
2021-03-24 22:44     ` Tammana, Gowtham [this message]

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=546c64e843c24ecab92584a279fc0bde@ti.com \
    --to=g-tammana@ti.com \
    --cc=denis@denix.org \
    --cc=meta-arago@arago-project.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.