7846 2015-06-04 11:44:23 +0000 devshell cannot be kept open across rebuilds 2020-11-19 16:04:59 +0000 1 1 7 Build System, Metadata & Runtime BitBake bitbake unspecified x86 Multiple RESOLVED WONTFIX Medium enhancement 4.99 1 igor.stoppa richard.purdie bluelightning poky.bs.watcher poky.watcher randy.macleod --- --- Don't know oldest_to_newest 51502 0 igor.stoppa 2015-06-04 11:44:23 +0000 I often use devshell to sketch portions of a bbclass function. This is useful to assess the correctness of the steps before launching a full build round. The process is iterative: 1 - try something in devshell (ex: bitbake -c devshell sometarget) 2 - modify the function accordingly 3 - test the function (ex: bitbake -c clean someothertarget && bitbake someothertarget) repeat However it is not comfortable, because having the devshell running prevents the testing, as bitbake will complain: "ERROR: Only one copy of bitbake should be run against a build directory". Workarounds are: - kill the devsell - remove the lockfile manually Would it be possible to allow the devshell to run in parallel to normal builds? 51511 1 richard.purdie 2015-06-04 14:57:40 +0000 Note that we need to allow bitbake to continue for devshell but it should pause for menuconfig. 88630 2 randy.macleod 2020-11-19 16:04:59 +0000 Not really a valid use case since the work dir could be removed or modifiied. Devshell requires the user to be aware of such limitations.