[yocto] What keeps sstate from being used?

[Daniel.]

Doesn't the sysroots live on tmp/sysroots? Doesn't the crosscompiler
and toolchains live in sysroots? Doesn't you need crosscompilers and
toolchains to compile everything else?

2016-07-06 8:51 GMT-03:00 Chris Z. <winotu.email at gmail.com>:
> Hi,
>
> Check:
> http://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#shared-state-cache
>
> "... the build system detects changes in the "inputs" to a given task by
> creating a checksum (or signature) of the task's inputs. If the checksum
> changes, the system assumes the inputs have changed and the task needs to be
> rerun. For the second question, the shared state (sstate) code tracks which
> tasks add which output to the build process.... "
>
>
> On Wed, Jul 6, 2016 at 12:10 PM, Gary Thomas <gary at mlbassoc.com> wrote:
>>
>> I just had a [nearly] complete build failed (building webkitgtk
>> after some 6000 tasks).  I decided to try the 'rebuild from sstate'
>> by removing my 'tmp' directory and rebuild.  Bitbake proceeded to
>> run 2200 setscene tasks and then [it seems] started over on the
>> build, rebuilding the target gcc, the kernel, who knows what else...
>> These are all things that I thought had been completed before
>> during the initial ~6000 steps.
>>
>> What could be going on and why couldn't it just pick up using
>> sstate from where it left off?
>>
>> --
>> ------------------------------------------------------------
>> Gary Thomas                 |  Consulting for the
>> MLB Associates              |    Embedded world
>> ------------------------------------------------------------
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>
>
>
> --
> _______________________________________________
> yocto mailing list
> yocto at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



-- 
"Do or do not. There is no try"
  Yoda Master