Re: [bitbake-devel] [PATCH v3 2/2] bitbake-setup: share sstate by default between builds

["Antonin Godard" <antonin.godard@bootlin.com>]

On Thu Jan 29, 2026 at 1:04 PM CET, Alexander Kanavin via lists.openembedded.org wrote:
[...]
> +            sstate_settings = textwrap.dedent(
> +                """
> +                #
> +                # Where to place shared-state files
> +                #
> +                # BitBake has the capability to accelerate builds based on previously built output.
> +                # This is done using "shared state" files which can be thought of as cache objects
> +                # and this option determines where those files are placed.
> +                #
> +                # You can wipe out TMPDIR leaving this directory intact and the build would regenerate
> +                # from these files if no changes were made to the configuration. If changes were made
> +                # to the configuration, only shared state files where the state was still valid would
> +                # be used (done using checksums).
> +                SSTATE_DIR ?= "{sstate_dir}"

Nitpicky I know , but we should add a line return here, as DL_DIR above is
already separated from SSTATE_DIR by a line return.

> +                #
> +                # Hash Equivalence database location
> +                #
> +                # Hash equivalence improves reuse of sstate by detecting when a given sstate
> +                # artifact can be reused as equivalent, even if the current task hash doesn't
> +                # match the one that generated the artifact. This variable controls where the
> +                # Hash Equivalence database ("hashserv.db") is stored and can be shared between
> +                # concurrent builds.
> +                BB_HASHSERVE_DB_DIR ?= "${{SSTATE_DIR}}"
> +                """.format(sstate_dir=os.path.join(top_dir, ".sstate-cache"))
> +            )

Antonin