From f044e03776652d4f822c2f3787142bda34364965 Mon Sep 17 00:00:00 2001 From: Thomas Petazzoni Date: Wed, 7 Mar 2012 20:26:50 +0100 Subject: ccache: set COMPILERCHECK to 'none' This allows ccache to re-use its cache contents even if the compiler binary mtime has changed. It is the simplest approach to solve this problem, and it works for the internal, external and crosstool-ng toolchain backends. Of course, it leaves the user responsible for invalidating the cache when necessary, but there doesn't seem to be a real good solution that allows both to: 1/ keep the cache contents accross builds and re-use it and 2/ invalidate the cache automatically when the compiler chances in an incompatible way. Signed-off-by: Thomas Petazzoni Signed-off-by: Peter Korsgaard --- package/ccache/ccache.mk | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) (limited to 'package/ccache') diff --git a/package/ccache/ccache.mk b/package/ccache/ccache.mk index 393989f54..f71376ee8 100644 --- a/package/ccache/ccache.mk +++ b/package/ccache/ccache.mk @@ -25,10 +25,18 @@ HOST_CCACHE_CONF_ENV = \ # has zero dependency besides the C library. HOST_CCACHE_CONF_OPT += ccache_cv_zlib_1_2_3=no -# We directly hardcode the cache location into the binary, as it is -# much easier to handle than passing an environment variable. +# We directly hardcode configuration into the binary, as it is much +# easier to handle than passing an environment variable. Our +# configuration is: +# - the cache location +# - the fact that ccache shouldn't use the compiler binary mtime to +# - detect a change in the compiler, because in the context of +# - Buildroot, that completely defeats the purpose of ccache. Of +# - course, that leaves the user responsible for purging its cache +# - when the compiler changes. define HOST_CCACHE_FIX_CCACHE_DIR sed -i 's,getenv("CCACHE_DIR"),"$(CCACHE_CACHE_DIR)",' $(@D)/ccache.c + sed -i 's,getenv("CCACHE_COMPILERCHECK"),"none",' $(@D)/ccache.c endef HOST_CCACHE_POST_CONFIGURE_HOOKS += \ -- cgit v1.2.3