|author||Thomas Petazzoni <email@example.com>||2012-03-07 20:26:50 +0100|
|committer||Peter Korsgaard <firstname.lastname@example.org>||2012-03-08 22:56:33 +0100|
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 <email@example.com> Signed-off-by: Peter Korsgaard <firstname.lastname@example.org>
Diffstat (limited to 'Config.in')
1 files changed, 7 insertions, 0 deletions
@@ -191,6 +191,13 @@ config BR2_CCACHE
up future builds. The cache is stored in
+ 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
bool "Show packages that are deprecated or obsolete"