From: Christopher Larson <clarson@kergoth.com>
To: Openembedded Discussion <openembedded-devel@lists.openembedded.org>
Subject: Re: How to force recipe to be parsed eveey time - dynamic PV value
Date: Fri, 18 Dec 2015 08:36:18 -0700 [thread overview]
Message-ID: <CABcZAN=9hSvADBTzvW7jL7maFhTU5vLO=i1RO1-UzQFVG4fdng@mail.gmail.com> (raw)
In-Reply-To: <1BDA3F91DD18BA459E26B6B10F84A8D7010AB82D@DEMUMBX004.nsn-intra.net>
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
prev parent reply other threads:[~2015-12-18 15:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 11:51 How to force recipe to be parsed eveey time - dynamic PV value Kubalski, Lukasz (EXT-Espotel - PL/Wroclaw)
2015-12-18 15:36 ` Christopher Larson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABcZAN=9hSvADBTzvW7jL7maFhTU5vLO=i1RO1-UzQFVG4fdng@mail.gmail.com' \
--to=clarson@kergoth.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.