From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/4 V4] bitbake: share source directory
Date: Tue, 28 Jun 2011 12:19:36 +0100 [thread overview]
Message-ID: <1309259976.20015.241.camel@rex> (raw)
In-Reply-To: <7abf11041890a833e554fb85ae2c958314ff1256.1309243115.git.liezhi.yang@windriver.com>
On Tue, 2011-06-28 at 17:05 +0800, Robert Yang wrote:
> This patch is derived from Richard, it is a quick proof of concept to
> show how source code could be shared between recipes which use ${B} to
> have a separate build directory compared to source directory ${S}.
>
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> ---
> bitbake/lib/bb/build.py | 4 ++--
> bitbake/lib/bb/cache.py | 3 +++
> bitbake/lib/bb/runqueue.py | 10 ++++++++++
> 3 files changed, 15 insertions(+), 2 deletions(-)
Since this is a bitbake patch it should really have gone to the
bitbake-devel list. Its been posted around enough times for review
though so I've merged it into bitbake. I did massively reword the commit
message though to reflect what the changes mean from a bitbake
perspective.
Cheers,
Richard
next prev parent reply other threads:[~2011-06-28 11:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 9:05 [PATCH 0/4 V4] Share gcc work directories Robert Yang
2011-06-28 9:05 ` [PATCH 1/4 V4] bitbake: share source directory Robert Yang
2011-06-28 11:19 ` Richard Purdie [this message]
2011-06-28 9:05 ` [PATCH 2/4 V4] Share gcc work directories Robert Yang
2011-06-28 9:05 ` [PATCH 3/4 V4] gcc-4.5.1: share " Robert Yang
2011-06-28 9:05 ` [PATCH 4/4 V4] gcc-4.6: " Robert Yang
2011-06-28 14:53 ` [PATCH 0/4 V4] Share gcc " Richard Purdie
2011-06-30 23:26 ` Saul Wold
2011-07-01 7:15 ` It's broken, please revert. " Koen Kooi
2011-07-01 8:10 ` Richard Purdie
2011-07-01 9:08 ` Koen Kooi
2011-07-01 11:28 ` Richard Purdie
2011-07-01 8:32 ` Richard Purdie
2011-07-01 11:00 ` Koen Kooi
2011-07-01 13:57 ` Khem Raj
2011-07-01 14:01 ` Koen Kooi
2011-07-01 16:55 ` 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=1309259976.20015.241.camel@rex \
--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