diff mbox

[2/2] classes/gobject-introspecton-data: lazy assign GI_DATA_ENABLED

Message ID 1473680885-30513-2-git-send-email-ross.burton@intel.com
State Accepted
Commit 75a5297369c7b04cef098e2a76f7f8f4781764aa
Headers show

Commit Message

Ross Burton Sept. 12, 2016, 11:48 a.m. UTC 
By letting a recipe assign GI_DATA_ENABLED trivially there is a simple and clear
way to disable gobject-introspection for specific build configurations.

Signed-off-by: Ross Burton <ross.burton@intel.com>

---
 meta/classes/gobject-introspection-data.bbclass | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

-- 
2.8.1

-- 
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
diff mbox

Patch

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)}"
-
-