diff options
| author | Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> | 2011-09-23 23:46:33 +0400 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-09-26 20:50:27 +0100 |
| commit | 982373006a98cf2303514badd1cfb692108408c0 (patch) | |
| tree | bfec5e08bb8db344232baba3f854b4341910e4da | |
| parent | 7b18b3c96634e40abf690a7ec72562389b0e6c23 (diff) | |
| download | openembedded-core-982373006a98cf2303514badd1cfb692108408c0.tar.gz openembedded-core-982373006a98cf2303514badd1cfb692108408c0.tar.bz2 openembedded-core-982373006a98cf2303514badd1cfb692108408c0.zip | |
bitbake.conf: change ccache path to use MULTIMACH_HOST_SYS
Currently if I build packages for several targets (e.g. for armv5te tosa
and for armv7a beagleboard) oe will use single ccache dir for both of
those targets: build/ccache/arm-oe-linux-gnueabi. However those targets
use different opcodes, different features and binaries created for one
of those targets wont't run on the lower one. So use MULTIMACH_HOST_SYS
for ccache dir, so that it uses something like
build/ccache/armv5te-oe-linux-gnueabi dir.
Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
| -rw-r--r-- | meta/conf/bitbake.conf | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf index b7bcc23890..730439c3b4 100644 --- a/meta/conf/bitbake.conf +++ b/meta/conf/bitbake.conf @@ -407,7 +407,7 @@ export PATH CCACHE = "${@bb.which(bb.data.getVar('PATH', d, 1), 'ccache') and 'ccache '}" TOOLCHAIN_OPTIONS = " --sysroot=${STAGING_DIR_TARGET}" -export CCACHE_DIR = "${TMPDIR}/ccache/${HOST_SYS}/${PN}" +export CCACHE_DIR = "${TMPDIR}/ccache/${MULTIMACH_HOST_SYS}/${PN}" export CC = "${CCACHE}${HOST_PREFIX}gcc ${HOST_CC_ARCH}${TOOLCHAIN_OPTIONS}" export CXX = "${CCACHE}${HOST_PREFIX}g++ ${HOST_CC_ARCH}${TOOLCHAIN_OPTIONS}" export F77 = "${CCACHE}${HOST_PREFIX}g77 ${HOST_CC_ARCH}${TOOLCHAIN_OPTIONS}" |