From: Gary Thomas <gary@mlbassoc.com>
To: Patrick Doyle <wpdster@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: How to specify a default value for a variable in a recipe
Date: Fri, 13 Jun 2014 08:13:51 -0600 [thread overview]
Message-ID: <539B071F.9020908@mlbassoc.com> (raw)
In-Reply-To: <CAF_dkJDSGM_CF34KF-+McY7S=ZvM+htzD1k0HMUDhRZHsdaOvQ@mail.gmail.com>
On 2014-06-13 08:07, Patrick Doyle wrote:
> On Fri, Jun 13, 2014 at 9:47 AM, Gary Thomas <gary@mlbassoc.com> wrote:
>> If this is in the gstxbac recipe itself, use the much simpler
>> SRCREV ?= "${AUTOREV}"
>
> Even better! While I like that solution best of all, that opens up a
> whole new world of hurt for me.
>
> How does
>
> SRCREV_default_pn-gstxbac = "${AUTOREV}"
>
> work? When would I use that over the much simpler solution you proposed?
>
> I am thinking that if I used your solution, I might place
>
> SRCREV_pn-gstxbac = "123" (or a git hash, or whatever)
>
> in my local.conf? in my BSP layer.conf?
>
> I guess I could put
>
> SRCREV_default_pn-gstxbac = "123" in my BSP layer.conf, and then,
> later on, on some other project that used the same board, I might put
>
> SRCREV_pn-gstxbac = "${AUTOREV}" in my local.conf, or maybe in a
> .bbappend file for my BSP?
>
> How/where does the _pn suffix (middlex?) come into play?
Any time you need to set the variable outside of the recipe itself (.bb* or .inc),
then you need the _pn-${recipe} syntax.
>
> At this point, I like your solution tremendously, as it makes sense to
> me. But I sure would like to understand more about all the myriad
> capabilities offered by bitbake.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2014-06-13 14:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 13:08 How to specify a default value for a variable in a recipe Patrick Doyle
2014-06-13 13:47 ` Gary Thomas
2014-06-13 14:07 ` Patrick Doyle
2014-06-13 14:13 ` Gary Thomas [this message]
2014-06-13 14:33 ` Patrick Doyle
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=539B071F.9020908@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=wpdster@gmail.com \
--cc=yocto@yoctoproject.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.