[gnome-continuous-yocto/gnomeostree-3.28-rocko: 2437/8267] classes/gobject-introspecton-data: lazy assign GI_DATA_ENABLED
- From: Emmanuele Bassi <ebassi src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-continuous-yocto/gnomeostree-3.28-rocko: 2437/8267] classes/gobject-introspecton-data: lazy assign GI_DATA_ENABLED
- Date: Sat, 16 Dec 2017 23:13:45 +0000 (UTC)
commit 7c2d1975729064aca427c93f9946c553d602948f
Author: Ross Burton <ross burton intel com>
Date: Mon Sep 12 12:46:26 2016 +0100
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>
meta/classes/gobject-introspection-data.bbclass | 4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
---
diff --git a/meta/classes/gobject-introspection-data.bbclass b/meta/classes/gobject-introspection-data.bbclass
index b1bdd26..2ef6846 100644
--- a/meta/classes/gobject-introspection-data.bbclass
+++ b/meta/classes/gobject-introspection-data.bbclass
@@ -3,7 +3,5 @@
#
# It should be used in recipes to determine whether introspection data should be built,
# so that qemu use can be avoided when necessary.
-GI_DATA_ENABLED = "${@bb.utils.contains('DISTRO_FEATURES', 'gobject-introspection-data', \
+GI_DATA_ENABLED ?= "${@bb.utils.contains('DISTRO_FEATURES', 'gobject-introspection-data', \
bb.utils.contains('MACHINE_FEATURES', 'qemu-usermode', 'True', 'False', d), 'False',
d)}"
-
-
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]