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 --- Config.in | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 'Config.in') diff --git a/Config.in b/Config.in index 8579a63b1..2002996fe 100644 --- a/Config.in +++ b/Config.in @@ -191,6 +191,13 @@ config BR2_CCACHE up future builds. The cache is stored in $HOME/.buildroot-ccache. + Note that Buildroot does not try to invalidate the cache + contents when the compiler changes in an incompatible + way. Therefore, if you make a change to the compiler version + and/or configuration, you are responsible for purging the + ccache cache by removing the $HOME/.buildroot-ccache + directory. + config BR2_DEPRECATED bool "Show packages that are deprecated or obsolete" help -- cgit v1.2.3