From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/4] classes: Add recipe class to overrides
Date: Fri, 24 Feb 2012 16:20:10 +0000 [thread overview]
Message-ID: <1330100410.5477.4.camel@ted> (raw)
In-Reply-To: <0c86983a495510f1fec576591e2f5d5e70cb4aa5.1330053959.git.raj.khem@gmail.com>
On Thu, 2012-02-23 at 19:33 -0800, Khem Raj wrote:
> We have currently no override to detect a recipe
> being build cross, crosssdk or for target
> at times we can use virtclass-native and virtclass-nativesdk to
> override stuff in recipes but we dont have way to modify a variables
> based on recipe type always.
>
> With this patch we attempt to have recipe class override always
> so we can use it in recipes which use BBCLASSEXTEND as well as
> others which inherit the classes directly.
>
> I am not too fond of names that I have used so any suggestions are
> welcome I would have liked to drop virtclass- from the existing
> overrides but that would mean a lot of changes so I left them
> alone.
>
> With this change now we can say
>
> EXTRA_OECONF_class-target = "...."
> EXTRA_OECONF_virtclass-native = "..."
> EXTRA_OECONF_virtclass-nativesdk = "..."
> EXTRA_OECONF_virtclass-crosssdk= "..."
I think we need to drop the "virt" here and make this consistent since
they are no longer specific to the virtual BBCLASSEXTEND code...
Cheers,
Richard
next prev parent reply other threads:[~2012-02-24 16:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 3:33 [PATCH 0/4] stash gcc-cross buildtree and add recipe class override Khem Raj
2012-02-24 3:33 ` [PATCH 1/4] glib-networking: Add intltools-native to DEPENDS Khem Raj
2012-02-24 3:33 ` [PATCH 2/4] classes: Add recipe class to overrides Khem Raj
2012-02-24 16:20 ` Richard Purdie [this message]
2012-02-24 17:02 ` Khem Raj
2012-02-24 3:33 ` [PATCH 3/4] default-distrovars: Add empty weak definition for DISTRO variable Khem Raj
2012-02-24 16:21 ` Richard Purdie
2012-02-24 17:05 ` Khem Raj
2012-03-05 21:36 ` Saul Wold
2012-03-05 23:02 ` Khem Raj
2012-03-22 1:23 ` Denys Dmytriyenko
2012-03-22 4:22 ` Khem Raj
2012-03-22 16:48 ` Khem Raj
2012-03-22 17:52 ` Richard Purdie
2012-02-24 3:33 ` [PATCH 4/4] gcc: Stash the gcc-cross builddir to reuse in libgcc and gcc-runtime Khem Raj
2012-02-27 19:57 ` [PATCH 0/4] stash gcc-cross buildtree and add recipe class override Khem Raj
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=1330100410.5477.4.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox