Bug 7846 - devshell cannot be kept open across rebuilds
Summary: devshell cannot be kept open across rebuilds
Status: RESOLVED WONTFIX
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium enhancement
Target Milestone: 4.99
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-06-04 11:44 UTC by Igor Stoppa
Modified: 2020-11-19 16:04 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Igor Stoppa 2015-06-04 11:44:23 UTC
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?
Comment 1 Richard Purdie 2015-06-04 14:57:40 UTC
Note that we need to allow bitbake to continue for devshell but it should pause for menuconfig.
Comment 2 Randy MacLeod 2020-11-19 16:04:59 UTC
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.