[yocto] autorev and shared-state issues
Luke (Lucas) Starrett
lstarret at broadcom.com
Tue Jan 26 11:47:55 PST 2016
Hi Chris,
I had been reading over PV and SRCPV earlier today and didn’t quite digest that this was necessary. I don’t know for sure that this is the “right” solution, but it does at least cause subsequent changes to be seen and built:
PV = "git${SRCPV}"
Seems like this should be documented in a little better detail.
Thanks, Luke.
From: kergoth at gmail.com [mailto:kergoth at gmail.com] On Behalf Of Christopher Larson
Sent: Tuesday, January 26, 2016 2:07 PM
To: Luke (Lucas) Starrett
Cc: yocto at yoctoproject.org
Subject: Re: [yocto] autorev and shared-state issues
On Tue, Jan 26, 2016 at 12:03 PM, Luke (Lucas) Starrett <lstarret at broadcom.com<mailto:lstarret at broadcom.com>> wrote:
I’m struggling with a behavior where even though we have a SRC_URI set to ${AUTOREV}, changes to the underlying git repository are not being seen on subsequent builds. I have reproduced this behavior across both a kernel and u-boot recipe, so it seems like a generic problem.
In general, how does autorev behave when used in conjunction with shared state? If the underlying git HEAD moves, shouldn’t this be seen and prevent re-use of prebuilt content in shared state?
We are currently based on the Fido/1.8.1 tag for this exercise.
My guess is you didn't add SRCPV to your PV, so changes to SRCREV aren't changing PV, and do_fetch's checksum isn't changing.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20160126/76036b95/attachment.html>
More information about the yocto
mailing list