Bug 8657

Summary: extensible SDK: improve handling for sanity checks
Product: [Build System, Metadata & Runtime] OE-Core Reporter: Paul Eggleton <bluelightning>
Component: devtools / tool chainAssignee: Paul Eggleton <bluelightning>
Status: RESOLVED FIXED QA Contact: Aníbal Limón <anibal.limon>
Severity: enhancement    
Priority: Medium+ CC: alexandru.c.georgescu, meta.mr.watcher, meta.watcher
Version: 2.0   
Target Milestone: 2.2 M3   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Paul Eggleton 2015-11-06 10:03:30 UTC 
When installing the extensible SDK, we don't get to run the sanity checks until the "preparing build system" step; if they fail we tell the user to look at a log file. It would be nice if we could either tell them up front before starting the install process, or at least tell them what to do to continue the process (i.e. run ext_sdk_prepare.sh rather than having to reinstall the SDK).
Comment 1 Paul Eggleton 2015-11-06 10:27:22 UTC 
We may also need to evaluate the sanity checks and determine if all of them make sense in an extensible SDK context.