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]

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 458990924bc3d7e9afe9595976fe9445bbd548de..9ccf90add3d83abc4df89276878aa188fa69c863 100644 (file)
--- 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"