diff options
author | Bruce Ashfield <bruce.ashfield@windriver.com> | 2017-08-23 15:20:20 -0400 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2017-08-24 09:37:11 +0100 |
commit | 156cf9e25f875a50f907e570d9b62cbc2c051133 (patch) | |
tree | 51080383495cb9540b695a9338913d9dd6783f79 /scripts/lib | |
parent | 6b799e4b315ee5a1eaba9f445b2ba7d37d1e0176 (diff) | |
download | openembedded-core-156cf9e25f875a50f907e570d9b62cbc2c051133.tar.gz openembedded-core-156cf9e25f875a50f907e570d9b62cbc2c051133.tar.bz2 openembedded-core-156cf9e25f875a50f907e570d9b62cbc2c051133.zip |
kernel-yocto: relax BSP definition test
commit 44aea7b873 [kernel-yocto: ensure that only valid BSPs are built]
introduced a new check to ensure that a valid BSP definition was found,
rather than building something that 'closely' matched the current
MACHINE.
This check breaks valid configurations which do not have a bsp
definition but are otherwise completely configured machines.
To allow both elements to co-exist (and not add warnings or errors
to otherwise valid builds), we first check to see if an empty bsp
definition was found, but then check to see if a defconfig was
provided.
If a defconfig has been provided, that is a sign that the board
configuration is complete and we should continue the build without
otherwise bothering the user.
Tested on meta-raspberrypi and linux-yocto*
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/lib')
0 files changed, 0 insertions, 0 deletions