android,compilation,android-source,cyanogenmod,ccache
There are multiple layers that matter here. At the top-level, you have (at least that's my impression from briefly looking at the build system) a make-system (or something similar). Make builds specific 'targets' by invoking commands. If a target already exists and is up-to-date (the source files on which it...
The major reason is because buildroot sets the CCACHE_COMPILERCHECK variable to 'none'. See ccache.mk in Buildroot. Buildroot does this for good reason: everytime they would rebuild the same compiler version (let's say gcc 4.8.0), all the ccache results would be thrown out, even if they're still valid. Additionally, it's possible...