| Summary: |
devshell cannot be kept open across rebuilds |
| Product: |
[Build System, Metadata & Runtime] BitBake
|
Reporter: |
Igor Stoppa <igor.stoppa> |
| Component: |
bitbake | Assignee: |
Richard Purdie <richard.purdie> |
| Status: |
RESOLVED
WONTFIX
|
QA Contact: |
|
| Severity: |
enhancement
|
|
|
| Priority: |
Medium
|
CC: |
bluelightning, poky.bs.watcher, poky.watcher, randy.macleod
|
| Version: |
unspecified | |
|
| Target Milestone: |
4.99 | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
Don't know
|
|---|
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?