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>
This commit is contained in:
parent
45c8cc1a58
commit
ae6d5f8096
|
@ -4,7 +4,7 @@ LIC_FILES_CHKSUM = "file://git/tools/kgit;beginline=5;endline=9;md5=d8d1d729a70c
|
|||
|
||||
DEPENDS = "git-native guilt-native"
|
||||
|
||||
SRCREV = "7a3170d96e142ce85a958f5b22e45f68f785f58d"
|
||||
SRCREV = "71ffb08c20022610363e68f9243350b7da020825"
|
||||
PR = "r12"
|
||||
PV = "0.1+git${SRCPV}"
|
||||
|
||||
|
|
Loading…
Reference in New Issue