[OE-core] [PATCH] sanity.bbclass: Move back to running at ConfigParsed time

Richard Purdie richard.purdie at linuxfoundation.org
Wed Sep 5 22:42:53 UTC 2012


On Wed, 2012-09-05 at 15:21 -0700, Chris Larson wrote:
> On Wed, Sep 5, 2012 at 7:27 AM, Richard Purdie
> <richard.purdie at linuxfoundation.org> wrote:
> > If we don't do this, users can get extremely confused errors since the sanity tests
> > happen too late (after parsing) and don't see the warnings.
> 
> Can you elaborate on this? This commit message is extremely unclear.
> If there's an open bug in bugzilla or something that could be referred
> to here, that'd be helpful.

Sorry, I should have elaborated.

Set an invalid MACHINE, try and build and you set all kinds of nasty
warnings and no sensible message about what is wrong.

Change LCONF_VERSION and you don't get the warning unless parsing
completes which it may or may not depending on the kind of change.

and so on.

The sanity.bbclass code is meant to be helpful in these scenarios and
when its most needed, it wasn't working.

FWIW, I think we do need to fix the way sanity is being triggered and
improve this (massively). Unfortunately I didn't have time to do that
right this second but lets file an enhancement request in the bugzilla
and lets see if we can improve things soon?

Cheers,

Richard






More information about the Openembedded-core mailing list