summaryrefslogtreecommitdiff
path: root/meta/recipes-kernel/kexec
diff options
context:
space:
mode:
authorBruce Ashfield <bruce.ashfield@windriver.com>2013-04-15 12:45:56 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-04-15 21:15:20 +0100
commit2d7b2478a3d48a5686afde790c378ee2f69b8e59 (patch)
treeba13282e65e58f01a5458d7f5f107f6c9c2a0531 /meta/recipes-kernel/kexec
parent826c18eb1c69f5e3689b5b0ef188f74ae930a050 (diff)
downloadopenembedded-core-2d7b2478a3d48a5686afde790c378ee2f69b8e59.tar.gz
openembedded-core-2d7b2478a3d48a5686afde790c378ee2f69b8e59.tar.bz2
openembedded-core-2d7b2478a3d48a5686afde790c378ee2f69b8e59.zip
kern-tools: fix custom repository BSP generation
Updating the SCRCREV to pick up the following fix updateme: use absolute path for generated BSP descriptions When a custom BSP is used, a top level BSP is generated by the tools and fed to the build system just as a user defined BSP would be located and passed. The location of the generated file is placed in the top_tgt file, which is used by subsequent stages. A relative path was being placed into top_tgt, which binds the build to a particular directory structure and working directory. The location of parts of the build have changed, and this relative path is no longer accurate. Changing it to an absolute path solve the build issues related to custom BSPs. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-kernel/kexec')
0 files changed, 0 insertions, 0 deletions