summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBruce Ashfield <bruce.ashfield@windriver.com>2017-02-01 10:30:35 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-02-05 09:20:21 +0000
commit1003615b866bfe196994bdc25d305ff5eace2715 (patch)
treea0d2b4e82383439da0f3bd12ad367370d112b5f2
parent3d2f5c60b69afe787624a1a175d57d0e46e8b638 (diff)
downloadopenembedded-core-contrib-1003615b866bfe196994bdc25d305ff5eace2715.tar.gz
openembedded-core-contrib-1003615b866bfe196994bdc25d305ff5eace2715.tar.bz2
openembedded-core-contrib-1003615b866bfe196994bdc25d305ff5eace2715.zip
kernel-yocto: log the BSP definition file
When debugging a kernel configuration issue, one of the first questions is "what BSP was used". To answer this qusetion, we log the BSP .scc file that was used to generate the kernel configuration in the kernel source meta directory. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com>
-rw-r--r--meta/classes/kernel-yocto.bbclass1
1 files changed, 1 insertions, 0 deletions
diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass
index 36f61c5694..a7b6356381 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -148,6 +148,7 @@ do_kernel_metadata() {
# run1: pull all the configuration fragments, no matter where they come from
elements="`echo -n ${bsp_definition} ${sccs} ${patches} ${KERNEL_FEATURES}`"
if [ -n "${elements}" ]; then
+ echo "${bsp_definition}}" > ${S}/${meta_dir}/bsp_definition
scc --force -o ${S}/${meta_dir}:cfg,merge,meta ${includes} ${bsp_definition} ${sccs} ${patches} ${KERNEL_FEATURES}
if [ $? -ne 0 ]; then
bbfatal_log "Could not generate configuration queue for ${KMACHINE}."