By letting a recipe assign GTKDOC_ENABLED trivially there is a simple and clear
way to disable gtk-doc for specific build configurations.
Signed-off-by: Ross Burton <ross.bur...@intel.com>
---
meta/classes/gtk-doc.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/gtk-doc.bbclass b/meta/classes/gtk-doc.bbclass
index b2b6239..297eac6 100644
--- a/meta/classes/gtk-doc.bbclass
+++ b/meta/classes/gtk-doc.bbclass
@@ -7,7 +7,7 @@
#
# It should be used in recipes to determine whether gtk-doc based
documentation should be built,
# so that qemu use can be avoided when necessary.
-GTKDOC_ENABLED = "${@bb.utils.contains('DISTRO_FEATURES', 'api-documentation',
\
+GTKDOC_ENABLED ?= "${@bb.utils.contains('DISTRO_FEATURES',
'api-documentation', \
bb.utils.contains('MACHINE_FEATURES', 'qemu-usermode',
'True', 'False', d), 'False', d)}"
EXTRA_OECONF_prepend_class-target = "${@bb.utils.contains('GTKDOC_ENABLED',
'True', '--enable-gtk-doc --enable-gtk-doc-html --disable-gtk-doc-pdf', \
--
2.8.1
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
