From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Cc: bitbake-dev@lists.berlios.de
Subject: Re: bitbake -b with BBCLASSEXTENDed recipes
Date: Mon, 15 Mar 2010 23:23:32 -0400 [thread overview]
Message-ID: <20100316032332.GA18102@denix.org> (raw)
In-Reply-To: <ly634xpm2z.fsf_-_@ensc-virt.intern.sigma-chemnitz.de>
On Mon, Mar 15, 2010 at 05:48:52PM +0100, Enrico Scholz wrote:
> Martin Jansa <martin.jansa@gmail.com> writes:
>
> > Is it possible to implement some support for old functionality like
> > bitbake -c clean -b path.to.recipe.with.BBCLASSEXTEND.bb
> > ...
> > It's really hard to implement something like prefixing -b path with
> > "virtual:native:"
>
> Bitbake must be patched for this; see
> https://www.cvg.de/people/ensc/0008-bbclassextend.patch
Care to send it to the bitbake-dev mailing list?
--
Denys
next prev parent reply other threads:[~2010-03-16 3:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 19:39 [RFC} glib-2.0 cleanup Frans Meulenbroeks
2010-02-28 20:05 ` Koen Kooi
2010-02-28 20:26 ` Frans Meulenbroeks
2010-02-28 21:40 ` Graham Gower
2010-03-01 15:15 ` Denys Dmytriyenko
2010-03-01 15:20 ` Frans Meulenbroeks
2010-03-01 15:25 ` Marcin Juszkiewicz
2010-03-06 19:36 ` Frans Meulenbroeks
2010-02-28 21:35 ` Michael 'Mickey' Lauer
2010-03-01 7:30 ` Frans Meulenbroeks
2010-03-01 14:35 ` Koen Kooi
2010-03-01 14:43 ` Dr. Michael Lauer
2010-03-01 15:02 ` bitbake -b with BBCLASSEXTENDed recipes Was: " Martin Jansa
2010-03-15 16:48 ` bitbake -b with BBCLASSEXTENDed recipes Enrico Scholz
2010-03-16 3:23 ` Denys Dmytriyenko [this message]
2010-03-17 8:48 ` Martin Jansa
2010-03-17 10:03 ` Enrico Scholz
2010-03-01 22:11 ` [RFC} glib-2.0 cleanup Khem Raj
2010-03-01 22:30 ` Denys Dmytriyenko
2010-03-01 22:34 ` Chris Larson
2010-03-01 22:49 ` Khem Raj
2010-03-01 22:51 ` Chris Larson
2010-03-01 23:04 ` Khem Raj
2010-03-01 23:26 ` Chris 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=20100316032332.GA18102@denix.org \
--to=denis@denix.org \
--cc=bitbake-dev@lists.berlios.de \
--cc=openembedded-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox