From: Richard Purdie <richard.purdie@intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: wenzong fan <wenzong.fan@windriver.com>
Subject: Re: [Yocto] The design document for ccache-native
Date: Thu, 09 Jun 2011 23:51:30 +0100 [thread overview]
Message-ID: <1307659890.15712.197.camel@rex> (raw)
In-Reply-To: <4DF14BE9.7080704@intel.com>
On Thu, 2011-06-09 at 15:40 -0700, Saul Wold wrote:
> On 06/02/2011 08:11 PM, wenzong fan wrote:
> > Hi Folks,
> >
> > Please help me to review the design document for ccache-native, and
> > I also have two questions about it, any answers or suggestions are
> > appreciated.
> >
> > * Feature name: ccache-native
> > Priority: P3; M2
> > Owner: Wenzong Fan
> > Summary: Integrate ccache-native to yocto
> >
> > * Description:
> > Bitbake supports the 'CCACHE Mechanism', but 'ccache' hasn't been
> > included by poky/yocto, just add it as a native tool.
> >
> > * Usage:
> > Build ccache as a native tool by default and enable it for speeding
> > target packages build.
> >
> > * Implementation:
> > 1) Copy bb file from OE upstream to:
> > meta/recipes-devtools/ccache/
> >
> > 2) Update bb file to get the latest ccache_3.1.5 and split the single
> > bb file to:
> > 'ccache_3.1.5.bb', 'ccache.inc'
> >
> > 3) Enable ccache in the native tools building.
> >
> You will need to have it be a dependency pretty early on in the build.
> Additionally, this is a bit a new part to this task, we want to have the
> default CCACHE_DIR for the build default to a directory in TMPDIR
> instead of the user's home directory. This will mean setting an
> environment variable somewhere early also.
There is a little more detail on:
https://wiki.yoctoproject.org/wiki/Yocto_1.1_Schedule
Specifically, "c) Set CCACHE on a per recipe basis. need to figure out
whether ccache data can be shared and under what circumstances."
so something like adding:
export CCACHE_DIR = "${TMPDIR}/ccache/${TARGET_SYS}/${PN}"
to bitbake.conf with a bit more thought into working out the right
components to add to the variable.
Cheers,
Richard
next prev parent reply other threads:[~2011-06-09 22:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4DE850E8.2050701@windriver.com>
2011-06-09 22:40 ` [Yocto] The design document for ccache-native Saul Wold
2011-06-09 22:51 ` Richard Purdie [this message]
2011-06-09 23:51 ` Tom Rini
2011-06-10 2:54 ` Khem Raj
2011-06-10 14:34 ` Tom Rini
2011-06-10 1:46 ` wenzong fan
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=1307659890.15712.197.camel@rex \
--to=richard.purdie@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=wenzong.fan@windriver.com \
/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