bitbake.conf: We only care about the absolute value of baselib
The value of baselib can be constructed in several different ways and from a sstate perspective we don't care how it was made up, we only care what the final value is. This uses the new functionality in bitbake to ensure we only include the value of baselib and not any intermediate dependencies. [YOCTO #1583] (From OE-Core rev: c38567894ebc31ac977f2bc89a076d0380bddcf8) (From OE-Core rev: 8b70cfe7a1768b8bf1e5b7e390276518e16f14af) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
71824019fb
commit
100002e4c6
|
@ -8,6 +8,7 @@
|
|||
|
||||
# Used by multilib code to change the library paths
|
||||
baselib = "${BASELIB}"
|
||||
baselib[vardepvalue] = "${baselib}"
|
||||
BASELIB = "lib"
|
||||
BASELIB_powerpc64 = "lib64"
|
||||
|
||||
|
|
Loading…
Reference in New Issue