From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-browser][PATCHv2] chromium-wayland: skip when CHROMIUM_ENABLE_WAYLAND isn't enabled
Date: Thu, 13 Oct 2016 20:41:21 +0200 [thread overview]
Message-ID: <20161013184121.18637-1-Martin.Jansa@gmail.com> (raw)
In-Reply-To: <20161013183247.GE2924@jama>
* 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 | 2 ++
1 file changed, 2 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..bbba147 100644
--- a/recipes-browser/chromium/chromium-wayland_48.0.2548.0.bb
+++ b/recipes-browser/chromium/chromium-wayland_48.0.2548.0.bb
@@ -28,6 +28,8 @@ python() {
if (d.getVar('CHROMIUM_ENABLE_WAYLAND', True) == '1'):
if bb.utils.contains('PACKAGECONFIG', 'component-build', True, False, d):
bb.fatal("Chromium 48 Wayland version cannot be built in component-mode")
+ else:
+ raise bb.parse.SkipPackage("CHROMIUM_ENABLE_WAYLAND isn't enabled")
}
CHROMIUM_WAYLAND_GYP_DEFINES = "use_ash=1 use_aura=1 chromeos=0 use_ozone=1 use_xkbcommon=1"
--
2.10.1
next prev parent reply other threads:[~2016-10-13 18:41 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
2016-10-13 18:41 ` Martin Jansa [this message]
2016-10-14 12:12 ` [meta-browser][PATCHv2] chromium-wayland: skip when CHROMIUM_ENABLE_WAYLAND isn't enabled 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=20161013184121.18637-1-Martin.Jansa@gmail.com \
--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