After some more digging I found it is because the KTYPE is defined as standard/base and the spp script can only find standard. Is this expected behavior and yocto-bsp should be fixed or a bug and spp should be fixed?
From: Davis, Michael Sent: Tuesday, December 05, 2017 4:45 PM To: '[email protected]' Subject: Error caused by kernel-yocto: ensure that only valid BSPs are built After upgrading rocko all my builds are failing with the following message. ERROR: linux-yocto-4.12.14+gitAUTOINC+e3c9041f48_1d685baca1-r0.1 do_kernel_metadata: Could not locate BSP definition for test/standard and no defconfig was provided The source of the issue seems to be commit 44aea7b87307795fe4e089c51d45afccaa2f6525. This includes a fresh BSP I created with yocto-bsp create, so the helper tools are generating examples that don't work. bsp_definition=$(spp ${includes} --find -DKMACHINE=${KMACHINE} -DKTYPE=${LINUX_KERNEL_TYPE}) always returns nothing even though I have .scc files defined. What is the new expected format to avoid this error? Thanks, Mike
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
