From 100002e4c6c2a96aa644987e3e1a1bdfadb95988 Mon Sep 17 00:00:00 2001 From: Richard Purdie Date: Thu, 24 Nov 2011 17:46:46 +0000 Subject: 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 --- meta/conf/bitbake.conf | 1 + 1 file changed, 1 insertion(+) (limited to 'meta/conf') diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf index 730439c3b4..b58cbef488 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" -- cgit v1.2.3-54-g00ecf