From: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
To: openembedded-devel@lists.openembedded.org
Cc: "Maksim Sisov" <msisov@igalia.com>,
"Raphael Kubo da Costa" <raphael.kubo.da.costa@intel.com>,
"Søren Andersen" <san@skov.dk>
Subject: Re: [meta-browser][PATCH] chromium-ozone-wayland: Stop depending on the system's wayland-scanner binary
Date: Thu, 27 Jun 2019 17:50:06 +0200 [thread overview]
Message-ID: <6rtvcbvxht.fsf@pengutronix.de> (raw)
In-Reply-To: <20190627133859.6843-1-u.oelmann@pengutronix.de>
Hi maintainers of meta-browser,
looking back in the mailing-list archives I got the impression that
meta-browser's development does not really take place here anymore these
days, but is pushed on on GitHub. Hence I prepared a pull request of
this thread's patch and would like to ask for review:
https://github.com/OSSystems/meta-browser/pull/278
Best regards
Ulrich
On Thu, Jun 27 2019 at 15:38 +0200, Ulrich Ölmann <u.oelmann@pengutronix.de> wrote:
> This commit re-applies the changes of the commit given below to the current
> chromium-ozone-wayland recipe as they got lost in the meantime.
>
> | commit cd88d7be61bc39726b8ecf7ddc19e6942bcf8cb4
> | Author: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
> | Date: Thu May 2 12:08:54 2019 +0200
> |
> | chromium-ozone-wayland: Stop depending on the system's wayland-scanner
> | binary
> |
> | So far, we were using Chromium's default GN path for the system
> | wayland-scanner binary, "/usr/bin/wayland-scanner", which may not be present
> | at all and which should never be used anyway. Instead, we now point to the
> | version built by the wayland-native recipe.
> |
> | Doing so of course requires depending on wayland-native in the first place,
> | and that requires adding back REQUIRED_DISTRO_FEATURES and a DEPENDS block
> | that got removed with no explanation when the recipe was updated to
> | M72 (commit 97876fab, "chromium: Update to 72.0.3626.81").
> |
> | Fixes #241
> |
> | Signed-off-by: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
>
> Fixes: 1f363e25cb7d ("chromium: Update to 74.0.3729.131")
> Signed-off-by: Ulrich Ölmann <u.oelmann@pengutronix.de>
> ---
> .../chromium/chromium-ozone-wayland_75.0.3770.100.bb | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/recipes-browser/chromium/chromium-ozone-wayland_75.0.3770.100.bb b/recipes-browser/chromium/chromium-ozone-wayland_75.0.3770.100.bb
> index 22afa52aec20..1e4ed2958d2d 100644
> --- a/recipes-browser/chromium/chromium-ozone-wayland_75.0.3770.100.bb
> +++ b/recipes-browser/chromium/chromium-ozone-wayland_75.0.3770.100.bb
> @@ -31,6 +31,15 @@ SRC_URI += " \
> file://0001-ozone-wayland-Fix-method-prototype-match.patch \
> "
>
> +REQUIRED_DISTRO_FEATURES = "wayland"
> +
> +DEPENDS += "\
> + libxkbcommon \
> + virtual/egl \
> + wayland \
> + wayland-native \
> +"
> +
> # Chromium can use v4l2 device for hardware accelerated video decoding. Make sure that
> # /dev/video-dec exists.
> PACKAGECONFIG[use-linux-v4l2] = "use_v4l2_codec=true use_v4lplugin=true use_linux_v4l2_only=true"
> @@ -42,6 +51,7 @@ GN_ARGS += "\
> ozone_platform_headless=true \
> ozone_platform_wayland=true \
> ozone_platform_x11=false \
> + system_wayland_scanner_path="${STAGING_BINDIR_NATIVE}/wayland-scanner" \
> use_xkbcommon=true \
> use_system_libwayland=true \
> use_system_minigbm=true \
--
Pengutronix e.K. | Ulrich Ölmann |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2019-06-27 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 13:38 [meta-browser][PATCH] chromium-ozone-wayland: Stop depending on the system's wayland-scanner binary Ulrich Ölmann
2019-06-27 15:50 ` Ulrich Ölmann [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=6rtvcbvxht.fsf@pengutronix.de \
--to=u.oelmann@pengutronix.de \
--cc=msisov@igalia.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raphael.kubo.da.costa@intel.com \
--cc=san@skov.dk \
/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