From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Chris Larson <clarson@kergoth.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [RFC PATCH 1/3] base.bbclass: Run oe_import before other INHERITs
Date: Wed, 26 Mar 2014 15:55:58 +0000 [thread overview]
Message-ID: <1395849358.24890.103.camel@ted> (raw)
In-Reply-To: <CABcZANkY+HBcQf4mxQkyFkmT+1RvyGOuQG_zKKbmzBoOGMNGwg@mail.gmail.com>
On Wed, 2014-03-26 at 08:34 -0700, Chris Larson wrote:
>
> On Wed, Mar 26, 2014 at 2:30 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> +# We need the oe module name space early (before INHERITs get
> added)
> +# and whilst ugly, abusing inherit like this is quite
> effective
> +BASEIMPORTS = "${@oe_import(d)}"
> +inherit ${BASEIMPORTS}
>
> Wouldn't OE_IMPORTED := "${@oe_import(d)}" work as well, or am I
> missing something?
That would work as well. I just came to the other solution though a
different route... :)
Cheers,
Richard
prev parent reply other threads:[~2014-03-26 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 9:30 [RFC PATCH 1/3] base.bbclass: Run oe_import before other INHERITs Richard Purdie
2014-03-26 15:34 ` Chris Larson
2014-03-26 15:55 ` Richard Purdie [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=1395849358.24890.103.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=clarson@kergoth.com \
--cc=openembedded-core@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.