bitbake.conf: We only care about the absolute value of baselib

Submitted by Richard Purdie on Nov. 24, 2011, 5:54 p.m. | Patch ID: 15417


Message ID 1322157292.10928.14.camel@ted
State Accepted
Commit c38567894ebc31ac977f2bc89a076d0380bddcf8
Headers show

Commit Message

Richard Purdie Nov. 24, 2011, 5:54 p.m.
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]

Signed-off-by: Richard Purdie <>

Patch hide | download patch | download mbox

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 01f064c..43d973d 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -8,6 +8,7 @@ 
 # Used by multilib code to change the library paths
 baselib = "${BASELIB}"
+baselib[vardepvalue] = "${baselib}"
 BASELIB = "lib"
 BASELIB_powerpc64 = "lib64"