summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/mtools
diff options
context:
space:
mode:
authorChase Maupin <Chase.Maupin@ti.com>2013-03-13 07:03:50 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-04-23 13:00:52 +0100
commit6b8dace6fa76aedb597bd12b7b925b19ebec1cd5 (patch)
tree1bc8be18654ea141cec8898865263bdd5a5bffe7 /meta/recipes-devtools/mtools
parent9267d8d35227bae6b98bd5d461d08feb565cc830 (diff)
downloadpoky-6b8dace6fa76aedb597bd12b7b925b19ebec1cd5.tar.gz
kernel bbclass: return to original directory in do_deploy
* During the base kernel_do_deploy function the directory is changed to DEPLOYDIR in order to do some cleanup and symlinking. However, the directory is not changed back to the original starting directory ${S} at the end. For append functions this means that the starting directory is not ${S} as expected but instead ${DEPLOYDIR}. For functions like the do_deploy_append in recipes-kernel/linux/linux-dtb.inc there is an assumption that you are still in the source directory and not the DEPLOYDIR. Without this change the .dtb files are not copied because the check for the existence of ${DTS_FILE} which is a relative path from the ${S} directory fails. This means that the .dtb files are not copied into the deploy directory and subsequently the deploy/images directory. In the log.do_deploy file you will see lines like: Warning: arch/arm/boot/dts/xxxxx.dts is not available! (From OE-Core rev: cfac9cc41c98eb1858bd3b0dee3dcc672d53f78b) Signed-off-by: Chase Maupin <Chase.Maupin@ti.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/mtools')
0 files changed, 0 insertions, 0 deletions