From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-browser][PATCH] chromium-wayland: add wayland to REQUIRED_DISTRO_FEATURES
Date: Thu, 13 Oct 2016 20:32:48 +0200 [thread overview]
Message-ID: <20161013183247.GE2924@jama> (raw)
In-Reply-To: <20161013142432.32326-1-Martin.Jansa@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2661 bytes --]
On Thu, Oct 13, 2016 at 04:24:32PM +0200, Martin Jansa wrote:
> * otherwise chromium-wayland recipe might build with CHROMIUM_ENABLE_WAYLAND 0 and then
> autodetect couple of x11 libraries
> chromium-wayland-48.0.2548.0: chromium-wayland rdepends on atk, but it isn't a build dependency, missing atk in DEPENDS or PACKAGECONFIG? [build-deps]
> chromium-wayland-48.0.2548.0: chromium-wayland rdepends on gdk-pixbuf, but it isn't a build dependency, missing gdk-pixbuf in DEPENDS or PACKAGECONFIG? [build-deps]
> chromium-wayland-48.0.2548.0: chromium-wayland rdepends on gtk+, but it isn't a build dependency, missing gtk+ in DEPENDS or PACKAGECONFIG? [build-deps]
> chromium-wayland-48.0.2548.0: chromium-wayland rdepends on libxcomposite, but it isn't a build dependency, missing libxcomposite in DEPENDS or PACKAGECONFIG? [build-deps]
> chromium-wayland-48.0.2548.0: chromium-wayland rdepends on libxcursor, but it isn't a build dependency, missing libxcursor in DEPENDS or PACKAGECONFIG? [build-deps]
> chromium-wayland-48.0.2548.0: chromium-wayland rdepends on libxscrnsaver, but it isn't a build dependency, missing libxscrnsaver in DEPENDS or PACKAGECONFIG? [build-deps]
>
> * reported a while ago in:
> http://lists.openembedded.org/pipermail/openembedded-devel/2016-September/109131.html
>
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
> recipes-browser/chromium/chromium-wayland_48.0.2548.0.bb | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/recipes-browser/chromium/chromium-wayland_48.0.2548.0.bb b/recipes-browser/chromium/chromium-wayland_48.0.2548.0.bb
> index f7ad2ce..bad3d71 100644
> --- a/recipes-browser/chromium/chromium-wayland_48.0.2548.0.bb
> +++ b/recipes-browser/chromium/chromium-wayland_48.0.2548.0.bb
> @@ -2,6 +2,9 @@ include chromium-browser.inc
>
> DEPENDS += "wayland libxkbcommon"
>
> +inherit distro_features_check
> +REQUIRED_DISTRO_FEATURES = "wayland"
This isn't enough, because when x11 is also in DISTRO_FEATURES it will
disable wayland support (so we should skip this recipe).
# $CHROMIUM_ENABLE_WAYLAND
# set
# /OE/build/oe-core/meta-browser/recipes-browser/chromium/chromium-browser.inc:109
# [_defaultval] "${@bb.utils.contains('DISTRO_FEATURES', 'x11', '0',
# bb.utils.contains('DISTRO_FEATURES', 'wayland', '1',
# '0', d),d)}"
CHROMIUM_ENABLE_WAYLAND="0"
> +
> SRC_URI += "\
> file://chromium-wayland/add_missing_stat_h_include.patch \
> file://0003-Remove-hard-coded-values-for-CC-and-CXX.patch \
> --
> 2.10.1
>
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 169 bytes --]
next prev parent reply other threads:[~2016-10-13 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 14:24 [meta-browser][PATCH] chromium-wayland: add wayland to REQUIRED_DISTRO_FEATURES Martin Jansa
2016-10-13 18:32 ` Martin Jansa [this message]
2016-10-13 18:41 ` [meta-browser][PATCHv2] chromium-wayland: skip when CHROMIUM_ENABLE_WAYLAND isn't enabled Martin Jansa
2016-10-14 12:12 ` Khem Raj
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=20161013183247.GE2924@jama \
--to=martin.jansa@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox