[oe] [meta-browser][PATCH 3/3] Remove conditional detection of CHROMIUM_ENABLE_WAYLAND
Jacobo Aragunde Pérez
jaragunde at igalia.com
Fri Nov 18 17:06:10 UTC 2016
It can be a source of problems, because you must have chosen the
correct recipe to build the wayland or x11 version of chromium.
Signed-off-by: Jacobo Aragunde Pérez <jaragunde at igalia.com>
---
recipes-browser/chromium/chromium-browser.inc | 6 ------
1 file changed, 6 deletions(-)
diff --git a/recipes-browser/chromium/chromium-browser.inc b/recipes-browser/chromium/chromium-browser.inc
index 4fb47fd..8c73207 100644
--- a/recipes-browser/chromium/chromium-browser.inc
+++ b/recipes-browser/chromium/chromium-browser.inc
@@ -102,12 +102,6 @@ PACKAGECONFIG[kiosk-mode] = ""
PACKAGECONFIG[proprietary-codecs] = ""
-# Conditionally add ozone-wayland and its patches to the Chromium sources
-# You can override this by setting CHROMIUM_ENABLE_WAYLAND=1 or CHROMIUM_ENABLE_WAYLAND=0 in local.conf
-CHROMIUM_ENABLE_WAYLAND ??= "${@bb.utils.contains('DISTRO_FEATURES', 'x11', '0', \
- bb.utils.contains('DISTRO_FEATURES', 'wayland', '1', \
- '0', d),d)}"
-
# ozone-wayland will be cloned into a directory with this name
OZONE_WAYLAND_GIT_DESTSUFFIX ?= "ozone-wayland-git"
# Use glob to filter out the patches that shall be applied against ozone-wayland.
--
2.1.4
More information about the Openembedded-devel
mailing list