How to force recipe to be parsed eveey time - dynamic PV value

How to force recipe to be parsed eveey time - dynamic PV value

[Kubalski, Lukasz (EXT-Espotel - PL/Wroclaw)]

I have problem that recipe is not always parsed.
Is it way to force it? Like checksum/signature/stamp invalidation?

Problem details:
   I need to have my PV to be generated dynamically e.g like PV = "${@my_get_version_func(d)}"

In such case recipe is not parsed every time (checksum doesn't change), PV is no reevaluated  and even my_get_version_func would return different value my image is not rebuilt.

Thanks for any suggestions.

Re: How to force recipe to be parsed eveey time - dynamic PV value

[Christopher Larson]

On Fri, Dec 18, 2015 at 4:51 AM, Kubalski, Lukasz (EXT-Espotel -
PL/Wroclaw) <lukasz.kubalski.ext@nokia.com> wrote:

> I have problem that recipe is not always parsed.
> Is it way to force it? Like checksum/signature/stamp invalidation?
>
> Problem details:
>    I need to have my PV to be generated dynamically e.g like PV =
> "${@my_get_version_func(d)}"
>
> In such case recipe is not parsed every time (checksum doesn't change), PV
> is no reevaluated  and even my_get_version_func would return different
> value my image is not rebuilt.
>

By default, inline python is not expanded when included in the metadata
checksumming, it's left as is. If you want the result of the calculation to
be included, you can use vardepvalue:

    PV[vardepvalue] = "${PV}"
-- 
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics