Re: [PATCH 5/5] ccache: separate cache based on cross compile

["Moessbauer, Felix" <felix.moessbauer@siemens.com>]

On Mon, 2022-12-19 at 17:29 +0300, Anton Mikanovich wrote:
> Mixing ccache generated by cross and native compilers makes the
> second
> run to stuck all the build.

Never saw this, but might depend on the ccache version.

> 
> Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
> ---
>  meta/conf/bitbake.conf | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index 98412e02..86ebb075 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -130,7 +130,7 @@ INHERIT += "${@'buildstats' if
> d.getVar('USE_BUILDSTATS') == '1' else ''}"
>  # Default values for ccache
>  USE_CCACHE ??= "0"
>  CCACHE_TOP_DIR ?= "${TMPDIR}/ccache"
> -CCACHE_DIR ?= "${CCACHE_TOP_DIR}/${DISTRO}-${DISTRO_ARCH}"
> +CCACHE_DIR ?= "${CCACHE_TOP_DIR}/${DISTRO}-${DISTRO_ARCH}-
> ${BUILD_HOST_ARCH}"

Please also update doc/user_manual.md.
In addition, the need for that is somehow problematic in CI systems,
where you feed in the CCACHE_DIR from the outside. We currently do not
allow to set the CCACHE_TOP_DIR via an env var, and CCACHE_TOP_DIR also
affects the task hash (while CCACHE_DIR does not).

But with the current logic, it would make much more sense to just set
the CCACHE_TOP_DIR and let ISAR handle the internal cache layout.

Felix

>  CCACHE_DEBUG ?= "0"
>  
>  include conf/local.conf
> -- 
> 2.17.1
>