| Summary: | Create Interactive bitbake commandline mode | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] BitBake | Reporter: | Saul Wold <sgw> |
| Component: | bitbake | Assignee: | Richard Purdie <richard.purdie> |
| Status: | NEW --- | QA Contact: | Apoorv <apoorv.sangal> |
| Severity: | enhancement | ||
| Priority: | Medium | CC: | akuster, alexandru.c.georgescu, belen.barros.pena, bluelightning, hongxu.jia, jason.wessel, jessica.zhang, jose.perez.carranza, liezhi.yang, michael.opdenacker, poky.bs.watcher, poky.watcher, randy.macleod, ross.burton, sgh |
| Version: | 5.99 | ||
| Target Milestone: | Future | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Yes (doc changes required) | |
| Bug Depends on: | 2681 | ||
| Bug Blocks: | 4687 | ||
|
Description
Saul Wold
2012-11-14 21:04:17 UTC
To quote me from another email: "We need to take a step back and figure out how bitbake commandline interaction should work. Part of this would be resurrecting some of those "old" commands and having a shell like interface to bitbake. There are patches from Jason on the mailing list which need looking at in this context related to logging. There are also components like an interactive python shell like devshell I'd like to see too." To further detail this, there are several things we'd like to see in an interactive mode to bitbake where you can directly run commands against the bitbake server to get information. There are several pieces available: * Chris Larson's bb command * parts of shell.py, the old bitbake -i code * Ability to run a shell in python context (python devshell) which would be useful on bitbake's configuration data store too * Jason Wessel's real time logging patches * Memory resident bitbake We really need to glue these all together to form one good interactive experience on the commandline. is this still a thing? Would also love to momentarily change the number of threads, without having to stop BitBake. A typical use case is when you need your desktop to be more responsive, or when you want to run another CPU intensive job (such as kernel compiling). |