ccache: support changing the output directory
When building in a different output directory than the original build, there will currently be a lot of ccache misses because in many cases there is some -I/... absolute path in the compilation. Ccache has an option CCACHE_BASEDIR to substitute absolute paths with relative paths, so they wil be the same in the hash (and in the output). Since there are some disadvantages to this path rewriting, it is made optional as BR2_CCACHE_USE_BASEDIR. It defaults to y because the usefulness of ccache is severely reduced without this option. In addition to CCACHE_BASEDIR, we also substitute away the occurences of $(HOST_DIR) in the calculation of the compiler hash. This is done regardless of the setting of BR2_CCACHE_USE_BASEDIR because it's quite harmless. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
This commit is contained in:
committed by
Peter Korsgaard
parent
f4682cf933
commit
1e97b27873
@@ -20,6 +20,10 @@ ifeq ($(BR2_CCACHE),y)
|
||||
TOOLCHAIN_WRAPPER_ARGS += -DBR_CCACHE
|
||||
endif
|
||||
|
||||
ifeq ($(BR2_CCACHE_USE_BASEDIR),y)
|
||||
TOOLCHAIN_WRAPPER_ARGS += -DBR_CCACHE_BASEDIR='"$(BASE_DIR)"'
|
||||
endif
|
||||
|
||||
# For simplicity, build directly into the install location
|
||||
define TOOLCHAIN_BUILD_WRAPPER
|
||||
$(Q)mkdir -p $(HOST_DIR)/usr/bin
|
||||
|
||||
Reference in New Issue
Block a user