From: Gary Thomas <gary@mlbassoc.com>
To: yocto@yoctoproject.org
Subject: Re: How to specify a default value for a variable in a recipe
Date: Fri, 13 Jun 2014 07:47:44 -0600 [thread overview]
Message-ID: <539B0100.5090603@mlbassoc.com> (raw)
In-Reply-To: <CAF_dkJB9T4VWSOma0sTeaec8js4-Bp58=s4AKRxT0JryCHp8NA@mail.gmail.com>
On 2014-06-13 07:08, Patrick Doyle wrote:
> OK, I've got to ask this, because it totally confuses me. I wrote a
> recipe to build a custom application (gstreamer plugin, actually) that
> I wanted to fetch from our SCM. Bitbake told me I needed to specify a
> source revision and even gave me a clue of what to put in. Looking at
> the development manual, I decided I wanted to use the latest revision
> from our repository by default, so I added the following line to my
> recipe:
>
> SRCREV_default_pn-gstxbac = "${AUTOREV}"
>
> But now I'm curious. Why couldn't I use (I haven't tried this yet)
>
> SRCREV_pn-gstxbac ?= "${AUTOREV}"
If this is in the gstxbac recipe itself, use the much simpler
SRCREV ?= "${AUTOREV}"
>
> and even more confusingly, why isn't the syntax something more like:
>
> SRCREV_pn-gstxbac_default = "${AUTOREV}"
>
> What's going on here?
>
> Does one syntax (BLAH_default vs BLAH ?=) get evaluated early in the
> bitbake process and the other get evaluated late?
>
> Does the location of the letters "default" in a variable name matter?
>
> At some point, I really need to wrap my head around Bitbake, it's
> syntax, and how it operates and internalize all of that.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2014-06-13 13:47 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 [this message]
2014-06-13 14:07 ` Patrick Doyle
2014-06-13 14:13 ` Gary Thomas
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=539B0100.5090603@mlbassoc.com \
--to=gary@mlbassoc.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.