diff options
| author | Bruce Ashfield <bruce.ashfield@windriver.com> | 2015-02-20 13:38:03 -0500 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2015-02-21 22:05:34 +0000 |
| commit | 726c6c1f5e912e07cbd9519f7364e5e15a2d0594 (patch) | |
| tree | 3733cd97c52e066f8aeab10286cf1ab9f975c05f /scripts/lib/scriptpath.py | |
| parent | 7e6147bdbf95ef8dee01a0f32b3c7d9355a75209 (diff) | |
| download | poky-726c6c1f5e912e07cbd9519f7364e5e15a2d0594.tar.gz | |
linux-yocto: warn when a generated BSP description is used
The meta data (in tree or out of tree) that describes a BSP, its patches
and configuration is not always available when a new/default or manually
configured machine is built.
When this happens, the tools generate a skeleton BSP and use a
architecture defconfig for the build. If this is by design, the build
is typically sane and everything works fine. If an existing BSP
description was expected, chances are that the resulting kernel will not
be correct.
To avoid surprising the user when a default/skeleton BSP is used for the
build, we can make it obvious to the user by emitting a warning like
the following:
WARNING: [kernel]: An auto generated BSP description was used, this normally indicates a misconfiguration.
Check that your machine (myqemux86-64) has an associated kernel description.
[YOCTO: #3383]
(From OE-Core rev: f4a460afc4e2676cbf1daaa1d6723da9e6146526)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'scripts/lib/scriptpath.py')
0 files changed, 0 insertions, 0 deletions