summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2012-09-14 08:41:59 (GMT)
committerSaul Wold <sgw@linux.intel.com>2012-09-15 01:39:18 (GMT)
commit2611db5d9c34d32ee388f776edbbb37c2fee04a2 (patch)
tree1e2919f533d725f7521cf8467e889c31989bf036
parentaeb336516b6b590f72f0fdfeb1c6817bc68294c6 (diff)
downloadpoky-2611db5d9c34d32ee388f776edbbb37c2fee04a2.tar.gz
bitbake.conf: Assign SRCPV so that it will be tracked correcting in the sstate checksum
Currently, SRCPV is just listed as having a value of ${@bb.fetch2.get_srcrev(d)} which isn't helpful. This can mean that if PV changes, two recipes can have the same sstate checksum despite having different PV values since the PV value itself isn't tracked anywhere. Adding this line means that the real PV value is expanded and recorded in the sstate checksum, meaning the sstate packages no longer overlap. This is critical in ensuring consistent builds for revipes using SRCPV. (From OE-Core rev: a9fffadec4fb60547257cb3d7496b6e39ed07be8) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--meta/conf/bitbake.conf1
1 files changed, 1 insertions, 0 deletions
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index 1d4a83d..9c51630 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -588,6 +588,7 @@ SRCDATE = "${DATE}"
588SRCREV ??= "INVALID" 588SRCREV ??= "INVALID"
589AUTOREV = "${@bb.fetch2.get_autorev(d)}" 589AUTOREV = "${@bb.fetch2.get_autorev(d)}"
590SRCPV = "${@bb.fetch2.get_srcrev(d)}" 590SRCPV = "${@bb.fetch2.get_srcrev(d)}"
591SRCPV[vardepvalue] = "${SRCPV}"
591 592
592SRC_URI = "" 593SRC_URI = ""
593 594