From: Saul Wold <saul.wold@intel.com>
To: wenzong fan <wenzong.fan@windriver.com>
Cc: "Purdie, Richard" <richard.purdie@intel.com>,
'Patches and discussions about the oe-core layer'
<openembedded-core@lists.openembedded.org>
Subject: Re: [Yocto] The design document for ccache-native
Date: Thu, 09 Jun 2011 15:40:41 -0700 [thread overview]
Message-ID: <4DF14BE9.7080704@intel.com> (raw)
In-Reply-To: <4DE850E8.2050701@windriver.com>
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.
> * Questions:
> 1) Do we want to add it as a target package? And which images should
> include it?
Yes, it should be included as part of any SDK image, to do this you
would add it to the task-core-sdk list.
> 2) How to add it into native tools build list and build it by default?
>
You use BBCLASSEXTEND = "native" in the recipe, that will give you the
native for free.
>
> Thanks
> Wenzong
>
next parent reply other threads:[~2011-06-09 22:45 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 ` Saul Wold [this message]
2011-06-09 22:51 ` [Yocto] The design document for ccache-native Richard Purdie
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=4DF14BE9.7080704@intel.com \
--to=saul.wold@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@intel.com \
--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