| Summary: | Prevent hob running without pre and post files | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] Hob | Reporter: | Joshua Lock - Disabled <josh> |
| Component: | hob | Assignee: | Joshua Lock - Disabled <josh> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | jessica.zhang, jiajun.xu, lianhao.lu, liping.ke, poky.bs.watcher, poky.watcher |
| Version: | unspecified | ||
| Target Milestone: | 1.1 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
I'd think we need to enforce using the separate conf file if user want to use hob bug 1441 is the correct way to handle this long term and will fix the issue of not being able to run without the wrapper script, short term we need to work around this and should likely error if the pre and post files aren't specified. Fixed |
If hob is run directly (bitbake -u hob) changes are written to the local.conf file directly and some of the changes we write cause an infinite recursion error at parse time (namely setting of BBFILES. bb.data_smart.ExpansionError: Failure expanding variable None, expression was ${BBFILES} /tmp/hob-images/*.bb which triggered exception RuntimeError: maximum recursion depth exceeded We either need to: a) Fix hob to work without the separate conf file b) warn when the separate conf file is not specified and don't run