summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRoss Burton <ross.burton@intel.com>2016-09-12 12:46:26 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-09-14 22:22:08 +0100
commit7c2d1975729064aca427c93f9946c553d602948f (patch)
treeb95da2eadf89c6fa06d7116ba1706ad3f1c394d5
parentfc9ddc2459f59f24154a50a7a1aa8461466a6c90 (diff)
downloadpoky-7c2d1975729064aca427c93f9946c553d602948f.tar.gz
classes/gobject-introspecton-data: lazy assign GI_DATA_ENABLED
By letting a recipe assign GI_DATA_ENABLED trivially there is a simple and clear way to disable gobject-introspection for specific build configurations. (From OE-Core rev: 75a5297369c7b04cef098e2a76f7f8f4781764aa) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--meta/classes/gobject-introspection-data.bbclass4
1 files changed, 1 insertions, 3 deletions
diff --git a/meta/classes/gobject-introspection-data.bbclass b/meta/classes/gobject-introspection-data.bbclass
index b1bdd268e6..2ef684626a 100644
--- a/meta/classes/gobject-introspection-data.bbclass
+++ b/meta/classes/gobject-introspection-data.bbclass
@@ -3,7 +3,5 @@
3# 3#
4# It should be used in recipes to determine whether introspection data should be built, 4# It should be used in recipes to determine whether introspection data should be built,
5# so that qemu use can be avoided when necessary. 5# so that qemu use can be avoided when necessary.
6GI_DATA_ENABLED = "${@bb.utils.contains('DISTRO_FEATURES', 'gobject-introspection-data', \ 6GI_DATA_ENABLED ?= "${@bb.utils.contains('DISTRO_FEATURES', 'gobject-introspection-data', \
7 bb.utils.contains('MACHINE_FEATURES', 'qemu-usermode', 'True', 'False', d), 'False', d)}" 7 bb.utils.contains('MACHINE_FEATURES', 'qemu-usermode', 'True', 'False', d), 'False', d)}"
8
9