diff options
author | Thomas Petazzoni <thomas.petazzoni@free-electrons.com> | 2012-03-07 20:26:50 +0100 |
---|---|---|
committer | Peter Korsgaard <jacmet@sunsite.dk> | 2012-03-08 22:56:33 +0100 |
commit | f044e03776652d4f822c2f3787142bda34364965 (patch) | |
tree | 51209efd567818919a10817e9364f457ce54b970 /package/Config.in | |
parent | 7ea11dafff37c5403432f691cf3c46d1d5566e46 (diff) | |
download | buildroot-novena-f044e03776652d4f822c2f3787142bda34364965.tar.gz buildroot-novena-f044e03776652d4f822c2f3787142bda34364965.zip |
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 <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Diffstat (limited to 'package/Config.in')
0 files changed, 0 insertions, 0 deletions