From: <wenzong.fan@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH 0/1] Integrate ccache-native
Date: Fri, 17 Jun 2011 17:19:13 +0800 [thread overview]
Message-ID: <cover.1308302102.git.wenzong.fan@windriver.com> (raw)
From: Wenzong Fan <wenzong.fan@windriver.com>
1) Add ccache as a native tool, for getting it built automatically make
it as the dependency of bzip2; Also, the ccache will be included by SDK
images;
2) Set CCACHE on a per recipe basis and add task 'mkccachedir' to create
the CCACHE_DIR while start a package building;
3) Remove the duplicate 'ccache.inc' from 'meta/class/'.
The following changes since commit 2163461ec94528ecf046a04edc5db3d2dd3a6b8b:
Tom Zanussi (1):
systemtap: remove non-core COMPATIBLE_MACHINES
are available in the git repository at:
git://git.pokylinux.org/poky-contrib wenzong/ccache
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=wenzong/ccache
Wenzong Fan (1):
ccache: Integrate ccache-native
meta/classes/base.bbclass | 1 +
meta/classes/ccache.bbclass | 21 +++++++++++++++++++++
meta/classes/ccache.inc | 11 -----------
meta/conf/bitbake.conf | 1 +
meta/recipes-core/tasks/task-core-sdk.bb | 1 +
meta/recipes-devtools/ccache/ccache.inc | 16 ++++++++++++++++
meta/recipes-devtools/ccache/ccache_3.1.5.bb | 8 ++++++++
meta/recipes-extended/bzip2/bzip2_1.0.6.bb | 2 ++
8 files changed, 50 insertions(+), 11 deletions(-)
create mode 100644 meta/classes/ccache.bbclass
delete mode 100644 meta/classes/ccache.inc
create mode 100644 meta/recipes-devtools/ccache/ccache.inc
create mode 100644 meta/recipes-devtools/ccache/ccache_3.1.5.bb
next reply other threads:[~2011-06-17 9:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 9:19 wenzong.fan [this message]
2011-06-17 9:19 ` [PATCH 1/1] ccache: Integrate ccache-native wenzong.fan
2011-06-22 15:53 ` Richard Purdie
2011-06-21 15:45 ` [PATCH 0/1] " Mark Hatle
2011-06-22 1:37 ` 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=cover.1308302102.git.wenzong.fan@windriver.com \
--to=wenzong.fan@windriver.com \
--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