summaryrefslogtreecommitdiffstats
path: root/meta-yocto-bsp
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 22:35:28 +0100
commitae6d5f8096dced1970f171b68149e4ab9875020f (patch)
tree9d27d8a44870375f74ecc46138cb584b607a25fc /meta-yocto-bsp
parent45c8cc1a58e7868f4603be08a86fef178edfc926 (diff)
downloadast2050-yocto-poky-ae6d5f8096dced1970f171b68149e4ab9875020f.zip
ast2050-yocto-poky-ae6d5f8096dced1970f171b68149e4ab9875020f.tar.gz
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. (From OE-Core rev: 2d7b2478a3d48a5686afde790c378ee2f69b8e59) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta-yocto-bsp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud