This makes it possible to test meta-intel with yocto-compat-layer.py against the default configuration in OE-core and might also be useful for some distros.
However, it begs one question: should meta-intel as a BSP layer contain these userspace recipes at all? FWIW, it now passes the current script: $ yocto-compat-layer.py -n /fast/work/meta-intelINFO: Detected layers: INFO: meta-intel: LayerType.BSP, /fast/work/meta-intel INFO: INFO: Setting up for meta-intel(LayerType.BSP), /fast/work/meta-intel INFO: Getting initial bitbake variables ... INFO: Getting initial signatures ... INFO: Adding layer meta-intel INFO: Starting to analyze: meta-intel INFO: ---------------------------------------------------------------------- INFO: test_bsp_defines_machines (bsp.BSPCompatLayer) ... ok INFO: test_bsp_no_set_machine (bsp.BSPCompatLayer) ... ok INFO: test_parse (common.CommonCompatLayer) ... ok INFO: test_readme (common.CommonCompatLayer) ... ok INFO: test_show_environment (common.CommonCompatLayer) ... ok INFO: test_signatures (common.CommonCompatLayer) ... ok INFO: skipped "DistroCompatLayer: Layer meta-intel isn't Distro one." INFO: INFO: ---------------------------------------------------------------------- INFO: Ran 6 tests in 21.837s INFO: INFO: OK (skipped=1) Patrick Ohly (1): meta-intel: support distro without OpenGL common/recipes-multimedia/libva/libva-intel-driver_1.7.3.bb | 4 +++- common/recipes-multimedia/libva/va-intel.bb | 4 ++++ common/recipes-multimedia/libyami/libyami-utils_1.1.0.bb | 4 +++- common/recipes-multimedia/libyami/libyami_1.1.0.bb | 4 +++- 4 files changed, 13 insertions(+), 3 deletions(-) base-commit: e726360655432ca8b509927f543f8acfb9b2330c -- git-series 0.9.1 -- _______________________________________________ meta-intel mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-intel
