I've been looking into setting up my own BSP layer based on the standard/beaglebone branch and I've run into some warnings I wasn't familiar with. I created a test BSP with the yocto-bsp tool and set MACHINE=test, (which is the name of my meta layer) then ran it. This produced several warnings:
WARNING: linux-yocto-4.4.10+gitAUTOINC+870134f4bf_13852755ec-r0.1 do_patch: After meta data application, the kernel tree branch is standard/test. WARNING: linux-yocto-4.4.10+gitAUTOINC+870134f4bf_13852755ec-r0.1 do_patch: The SRC_URI specified branch standard/base. WARNING: linux-yocto-4.4.10+gitAUTOINC+870134f4bf_13852755ec-r0.1 do_patch: WARNING: linux-yocto-4.4.10+gitAUTOINC+870134f4bf_13852755ec-r0.1 do_patch: The branch will be forced to standard/base, but this means the board meta data WARNING: linux-yocto-4.4.10+gitAUTOINC+870134f4bf_13852755ec-r0.1 do_patch: (.scc files) do not match the SRC_URI specification. WARNING: linux-yocto-4.4.10+gitAUTOINC+870134f4bf_13852755ec-r0.1 do_patch: WARNING: linux-yocto-4.4.10+gitAUTOINC+870134f4bf_13852755ec-r0.1 do_patch: The meta data and branch standard/base should be inspected to ensure the proper WARNING: linux-yocto-4.4.10+gitAUTOINC+870134f4bf_13852755ec-r0.1 do_patch: kernel is being built. I found the patch which enabled this warning, but I'm unsure how to alleviate it. I do intend to use the standard/test branch, but I'm not sure which SRC_URI is telling bitbake to build the standard/base. Any idea where to start looking? Patch that enabled the warnings: http://lists.openembedded.org/pipermail/openembedded-core/2016-April/119808.html -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
