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>
This commit is contained in:
parent
fc9ddc2459
commit
7c2d197572
|
@ -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)}"
|
||||
|
||||
|
||||
|
|
Loading…
Reference in New Issue