All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Key expansion and overrides?
Date: Thu, 26 Mar 2015 14:30:16 +0000	[thread overview]
Message-ID: <1427380216.14020.100.camel@linuxfoundation.org> (raw)

Two interesting test cases:

OVERIDES = "myoverride"
TESTME = "myoverride"
FOO = "1"
FOO_${TESTME} = "2"

FOO = 1 or 2?

OVERIDES = "myoverride"
TESTME = "myoverride"
FOO = "1 2"
FOO_remove_${TESTME} = "2"

FOO = "1 2" or "1"?

Currently expansion in overrides doesn't work. I discovered this trying
to do:

X_remove_pn-gcc-cross-${TARGET_ARCH} = "Y"

which I do believe is a valid thing to attempt.

There are two ways of fixing this I guess. One is to call expandKeys()
before and after update_data() but I suspect we can still cases which
won't work. The other is to move to a model where overrides are applied
more dynamically and we lose the need for update_data(). There may be
some performance penalty for it.

I'm leaning towards trying to kill off update_data() right now...

Thoughts/comments welcome.

Cheers,

Richard





             reply	other threads:[~2015-03-26 14:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 14:30 Richard Purdie [this message]
2015-03-26 15:23 ` Key expansion and overrides? Christopher Larson

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=1427380216.14020.100.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-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.