From: Richard Purdie <rpurdie@linux.intel.com>
To: Chris Larson <clarson@kergoth.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: [PATCH 1/1] curl: fix native dependency
Date: Mon, 29 Nov 2010 04:25:57 -0800 [thread overview]
Message-ID: <1291033557.14277.944.camel@rex> (raw)
In-Reply-To: <AANLkTi=oxv9goiEMAfpkDAvq7n_GfGUMSXsonXDdzixd@mail.gmail.com>
On Sun, 2010-11-28 at 22:53 -0700, Chris Larson wrote:
> On Sun, Nov 28, 2010 at 10:26 PM, Tian, Kevin <kevin.tian@intel.com> wrote:
> > This also confuses me a bit. When virtclass-native is expanded, EXTRA_OECONF_append
> > is simply a variable. In that case the expanded value should override the 1st assignment
> > of EXTRA_OECONF_append, and then we should get:
> >
> > EXTRA_OECONF_append = " --without-gnutls "
> >
> > and then that's what we expect.
> >
> > I guess I may still overlook something here, and really appreciate your explanation
> > on the whole flow which is helpful. :-)
>
> No, EXTRA_OECONF_append is never a variable. _append/_prepend are
> operations, not part of the name. The value gets set aside in a list
> of appends for that variable. One _append cannot override/replace
> another on the same variable, its always cumulative.
Right.
Interestingly though, if I add this to curl*.bb:
FOO = "A"
FOO_append = "B"
FOO_append_virtclass-native = "C"
and then "bitbake curl-native -e | grep FOO" (he recipe has a
BBCLASSEXTEND native) what should I see?
I see FOO = "AB" which is not what I thought it would do...
Cheers,
Richard
next prev parent reply other threads:[~2010-11-29 12:26 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-17 8:32 [PATCH 0/1] curl-native build fix Qing He
2010-11-17 8:26 ` [PATCH 1/1] curl: fix native dependency Qing He
2010-11-28 14:22 ` Richard Purdie
2010-11-29 5:26 ` Tian, Kevin
2010-11-29 5:53 ` Chris Larson
2010-11-29 5:58 ` Tian, Kevin
2010-11-29 12:25 ` Richard Purdie [this message]
2010-11-29 13:04 ` Frans Meulenbroeks
2010-11-29 15:17 ` Richard Purdie
2010-12-05 9:48 ` Tian, Kevin
2010-11-29 15:24 ` Chris Larson
2010-12-05 9:32 ` Tian, Kevin
2010-12-06 1:04 ` Richard Purdie
2010-12-07 7:55 ` Tian, Kevin
2010-12-07 12:37 ` Richard Purdie
2010-12-08 3:12 ` Qing He
2010-12-09 15:16 ` Richard Purdie
2010-12-13 5:52 ` Qing He
2010-12-13 10:48 ` Qing He
2010-11-30 1:44 ` Qing He
2010-12-05 9:43 ` Tian, Kevin
2010-12-06 1:10 ` Richard Purdie
2010-12-07 7:56 ` Tian, Kevin
2010-11-29 8:17 ` Qing He
2010-11-29 11:57 ` Richard Purdie
2010-11-17 18:21 ` [PATCH 0/1] curl-native build fix Saul Wold
2010-11-17 18:26 ` Scott Garman
2010-11-19 22:43 ` Saul Wold
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=1291033557.14277.944.camel@rex \
--to=rpurdie@linux.intel.com \
--cc=clarson@kergoth.com \
--cc=poky@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox