sstate: Exclude SSTATE_EXTRAPATH from checksums

Submitted by Richard Purdie on Feb. 11, 2014, 2:52 p.m. | Patch ID: 66579


Message ID 1392130342.7120.155.camel@ted
State Accepted
Commit 1fa7d4331d994b9eeb6f973d1a1f04cb4df92c13
Headers show

Commit Message

Richard Purdie Feb. 11, 2014, 2:52 p.m.
After the change to allow target recipes to depend on native recipes, the
native checksums becomes all the more critical. Add to this that we're now
accounting for pre/postfuncs and we have a cache reuse issue since the
distro LSB string is getting coded in when it shouldn't be.

This excludes that string and allows one set of native sstate to share
checksums with another set from a different host distro. They're separated
into different directories so this is fine for our use cases.

Signed-off-by: Richard Purdie <>

Patch hide | download patch | download mbox

diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass
index ec9c546..f7bd117 100644
--- a/meta/classes/sstate.bbclass
+++ b/meta/classes/sstate.bbclass
@@ -17,6 +17,10 @@  SSTATE_EXTRAPATH   = ""
+# We don't want the sstate to depend on things like the distro string
+# of the system, we let the sstate paths take care of this.
+SSTATE_EXTRAPATH[vardepvalue] = ""
 # Also need to make cross recipes append to ${PN} and install once for any given PACAGE_ARCH so
 # can avoid multiple installs (e.g. routerstationpro+qemumips both using mips32)