Lines Matching refs:sstate

84 ``do_deploy`` as a shared state (sstate) task that can be accelerated
85 through sstate use. The sstate mechanism takes care of copying the
91    the sstate mechanism to malfunction.
395 The ``do_populate_sysroot`` task is a shared state (sstate) task, which
396 means that the task can be accelerated through sstate use. Realize also
461 :ref:`sstate <overview-manual/concepts:shared state cache>` cache files.
463 after cleaning, output files are simply restored from the sstate cache.
464 If you want to remove the sstate cache files for the recipe, you need to
474 (:ref:`sstate <overview-manual/concepts:shared state cache>`) cache, and
494 (:ref:`sstate <overview-manual/concepts:shared state cache>`) cache for a
497 shared state (:ref:`sstate <overview-manual/concepts:shared state cache>`)
505 no longer uses any sstate. Consequently, building the recipe from
510    The ``do_cleansstate`` task cannot remove sstate from a remote sstate