Bug 9128

Summary: "Using a development shell" section should clarify that commands in a devshell should match the commands that are run by bitbake
Product: [Documentation] Development Manual Reporter: Joshua Lock <joshuagloe>
Component: developmentAssignee: Scott Rifenbark <srifenbark>
Status: VERIFIED DUPLICATE QA Contact: Bogdan Alexandru Voiculescu <bogdanx.a.voiculescu>
Severity: normal    
Priority: Undecided CC: bogdanx.a.voiculescu
Version: unspecified   
Target Milestone: ---   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Joshua Lock 2016-02-17 15:24:56 UTC 
Some developers expect that once in a devshell they can call commands as if in a normal shell, whereas the reality is that the devshell is a mechanism to get into the bitbake task execution environment and commands must be called in the same manner as bitbake calls them i.e. with appropriate options for cross-compilation, etc.

We should update the "Using the development shell" section of the developer manual to make this clearer.

Furthermore we could point out that a user can use the run.do_* files in temp to a) look at how the tasks are run by bitbake and b) run the commands exactly as bitbake does.

i.e. if I'm in a devshell for connman in a build directory where connman has already built I can re-run the compilation steps by calling ../temp/run.do_compile
Comment 1 Joshua Lock 2016-02-18 15:42:30 UTC 
Turns out a remarkably similar bug was filed a couple of days before this.

*** This bug has been marked as a duplicate of bug 9114 ***
Comment 2 Scott Rifenbark 2016-02-18 17:27:37 UTC 
I set the doc flag to "No" here since it is a duplicate.
Comment 3 Bogdan Alexandru Voiculescu 2016-03-07 15:55:12 UTC 
verified