aboutsummaryrefslogtreecommitdiffstats
path: root/documentation/dev-manual
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2016-02-18 09:30:13 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-03-03 17:40:11 +0000
commita1970eb17bc8fde08aeca1128d5286c0bbc88ebf (patch)
tree3ef12c06b883dbc273c0e7d360a5ab9c1ffe73f5 /documentation/dev-manual
parenta58cde0857bfff01c9f3476e2ac27cf2c92e0fe2 (diff)
downloadopenembedded-core-contrib-a1970eb17bc8fde08aeca1128d5286c0bbc88ebf.tar.gz
dev-manual: Updated devshell section.
Fixes [YOCTO #9114] Added more detail on how to run commands from within the devshell. (From yocto-docs rev: 6535a8b80bbad3a4ece191c7e5a145ef5e09f1e2) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/dev-manual')
-rw-r--r--documentation/dev-manual/dev-manual-model.xml27
1 files changed, 25 insertions, 2 deletions
diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml
index f82a489fac..cad204d3b7 100644
--- a/documentation/dev-manual/dev-manual-model.xml
+++ b/documentation/dev-manual/dev-manual-model.xml
@@ -2832,10 +2832,33 @@
</para>
<para>
- When you are finished, you just exit the shell or close the terminal window.
+ To manually run a specific task using <filename>devshell</filename>,
+ run the corresponding <filename>run.*</filename> script in
+ the
+ <filename>${</filename><ulink url='&YOCTO_DOCS_REF_URL;#var-WORKDIR'><filename>WORKDIR</filename></ulink><filename>}/temp</filename>
+ (e.g., <filename>run.do_configure.</filename><replaceable>pid</replaceable>).
+ If a task's script does not exist, which would be the case if the task was
+ skipped by way of the sstate cache, you can create the task by first running
+ it outside of the <filename>devshell</filename>:
+ <literallayout class='monospaced'>
+ $ bitbake -c <replaceable>task</replaceable>
+ </literallayout>
+ </para>
+
+ <para>
+ Remember, that the <filename>devshell</filename> is a mechanism that allows
+ you to get into the BitBake task execution environment.
+ And as such, all commands must be called just as BitBake would call them.
+ That means you need to provide the appropriate options for
+ cross-compilation and so forth as applicable.
+ </para>
+
+ <para>
+ When you are finished using <filename>devshell</filename>, exit the shell
+ or close the terminal window.
</para>
- <note>
+ <note><title>Notes</title>
<para>
It is worth remembering that when using <filename>devshell</filename>
you need to use the full compiler name such as <filename>arm-poky-linux-gnueabi-gcc</filename>