3433 2012-11-14 21:04:17 +0000 Create Interactive bitbake commandline mode 2026-05-21 15:24:51 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake 5.99 x86 Multiple NEW Medium enhancement Future 2681 4687 1 sgw richard.purdie 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 apoorv.sangal --- --- Yes (doc changes required) oldest_to_newest 27448 0 sgw 2012-11-14 21:04:17 +0000 27468 1 richard.purdie 2012-11-15 11:08:44 +0000 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." 38428 2 richard.purdie 2013-11-01 14:54:18 +0000 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. 85928 3 akuster 2019-12-22 20:37:18 +0000 is this still a thing? 92580 4 michael.opdenacker 2022-02-17 16:29:59 +0000 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).