Re: [PATCH 1/8] bitbake.conf: remove 'gobject-introspection-data' from DISTRO/MACHINE_FEATURES_BACKFILL

[Alexander Kanavin <alexander.kanavin@linux.intel.com>]

On 03/18/2016 01:08 PM, Andre McCurdy wrote:

> Deciding if/how qemu can run binaries for each tuning target is
> already partially addressed by the QEMU_EXTRAOPTIONS logic in
> qemu.bbclass. My suggestion would be to somehow generalise that
> existing logic, so (at least for machines using one of the standard
> oe-core tuning files) the question "can qemu run binaries created for
> ${MACHINE}?" could be answered automatically.

I agree: machine features should specify the capabilities of a machine, 
and 'generate of gobject introspection data' is only a specific 
application of 'machine has qemu usermode support' feature. We might 
have other uses for qemu userspace in the future, for example gtkdoc 
generation.

So I'm thinking of having a machine feature called 'qemu-usermode', 
which is turned on by default, and can be disabled in specific machine 
configurations. And then a distro feature called 'gobject introspection 
data', which is on or off depending on whether the machine supports it, 
but can also be turned off explicitly. And then the recipes and recipe 
classes do the right thing. How's that?


Alex