[OE-core] [PATCH] populate_sdk_ext: Log the "Preparing build system" step

[Randy Witt]

On 03/25/2015 10:31 AM, Christopher Larson wrote:
> On Tue, Mar 24, 2015 at 5:16 PM, Randy Witt <randy.e.witt at linux.intel.com>
> wrote:
>
>> When using bitbake to do the setscene as part of sdk setup, it would be
>> useful to have a log in the case where it fails.
>>
>> The log is called preparing_build_system.log and is in the top level
>> directory of the extracted sdk.
>>
>> Signed-off-by: Randy Witt <randy.e.witt at linux.intel.com>
>>
>
> Is this step just doing a setscene from shipped sstate, or is it intended
> to build anything from scratch? Because I've seen cases where the sstate
> isn't used as it should be, and it ends up taking ages to run real tasks.
>

It should be using the shipped sstate based on the locked-sigs.inc file. I would 
expect it to fail if the signatures didn't match for some reason, but perhaps a 
change went in that changed behavior.

If you see an instance where it is not using the shipped sstate, could you file 
a bug or send an email? I'm really curious as to why it doesn't fail outright, 
because that's the whole point of the locked-sigs.inc file.