summaryrefslogtreecommitdiffstats
path: root/meta
diff options
context:
space:
mode:
authorAlexander Kanavin <alex.kanavin@gmail.com>2019-01-23 17:17:35 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2019-01-24 17:45:25 +0000
commitcc4e883a5413c67d647534c3d5afef1cd160f40a (patch)
treec8f1c9258411b772005133f43f69c3be4404726d /meta
parentba0b32ebc3520c367915657b8fb8878be5bfde92 (diff)
downloadpoky-cc4e883a5413c67d647534c3d5afef1cd160f40a.tar.gz
sstate.bbclass: make sure changes to SSTATE_SCAN_FILES are not ignored
When changing the SSTATE_SCAN_FILES variable in a recipe it doesn't cause a rebuild, so if there's a sstate-cache available with "bad" sstate data in it that will still be used even though the recipe is updated to address this. [YOCTO #13144] (From OE-Core rev: ea3526961920a229e0bb5fb459952be89fce2255) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta')
-rw-r--r--meta/classes/sstate.bbclass1
1 files changed, 1 insertions, 0 deletions
diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass
index 2f0bbd2d7d..6f51d9c187 100644
--- a/meta/classes/sstate.bbclass
+++ b/meta/classes/sstate.bbclass
@@ -62,6 +62,7 @@ SSTATE_ARCHS = " \
62SSTATE_MANMACH ?= "${SSTATE_PKGARCH}" 62SSTATE_MANMACH ?= "${SSTATE_PKGARCH}"
63 63
64SSTATECREATEFUNCS = "sstate_hardcode_path" 64SSTATECREATEFUNCS = "sstate_hardcode_path"
65SSTATECREATEFUNCS[vardeps] = "SSTATE_SCAN_FILES"
65SSTATEPOSTCREATEFUNCS = "" 66SSTATEPOSTCREATEFUNCS = ""
66SSTATEPREINSTFUNCS = "" 67SSTATEPREINSTFUNCS = ""
67SSTATEPOSTUNPACKFUNCS = "sstate_hardcode_path_unpack" 68SSTATEPOSTUNPACKFUNCS = "sstate_hardcode_path_unpack"