dev-manual: Applied review comments to devshell section.
Fixes [YOCTO #9114] Added a "Notes" box to address run script naming points and the fact that running a task's script is identical to what BitBake would do when it runs the task. (From yocto-docs rev: ddfba59743c977a3a3483ed9053434d3c622f698) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
3b410498fe
commit
d346c35b19
|
@ -2843,6 +2843,21 @@
|
||||||
<literallayout class='monospaced'>
|
<literallayout class='monospaced'>
|
||||||
$ bitbake -c <replaceable>task</replaceable>
|
$ bitbake -c <replaceable>task</replaceable>
|
||||||
</literallayout>
|
</literallayout>
|
||||||
|
<note><title>Notes</title>
|
||||||
|
<itemizedlist>
|
||||||
|
<listitem><para>Execution of a task's <filename>run.*</filename>
|
||||||
|
script and BitBake's execution of a task are identical.
|
||||||
|
In other words, running the script re-runs the task
|
||||||
|
just as it would be run using the
|
||||||
|
<filename>bitbake -c</filename> command.
|
||||||
|
</para></listitem>
|
||||||
|
<listitem><para>Any <filename>run.*</filename> file that doe not
|
||||||
|
have a <filename>.pid</filename> extension is a
|
||||||
|
symbolic link (symlink) to the most recent version of that
|
||||||
|
file.
|
||||||
|
</para></listitem>
|
||||||
|
</itemizedlist>
|
||||||
|
</note>
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
|
@ -2859,20 +2874,21 @@
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<note><title>Notes</title>
|
<note><title>Notes</title>
|
||||||
<para>
|
<itemizedlist>
|
||||||
It is worth remembering that when using <filename>devshell</filename>
|
<listitem><para>
|
||||||
you need to use the full compiler name such as <filename>arm-poky-linux-gnueabi-gcc</filename>
|
It is worth remembering that when using <filename>devshell</filename>
|
||||||
instead of just using <filename>gcc</filename>.
|
you need to use the full compiler name such as <filename>arm-poky-linux-gnueabi-gcc</filename>
|
||||||
The same applies to other applications such as <filename>binutils</filename>,
|
instead of just using <filename>gcc</filename>.
|
||||||
<filename>libtool</filename> and so forth.
|
The same applies to other applications such as <filename>binutils</filename>,
|
||||||
BitBake sets up environment variables such as <filename>CC</filename>
|
<filename>libtool</filename> and so forth.
|
||||||
to assist applications, such as <filename>make</filename> to find the correct tools.
|
BitBake sets up environment variables such as <filename>CC</filename>
|
||||||
</para>
|
to assist applications, such as <filename>make</filename> to find the correct tools.
|
||||||
|
</para></listitem>
|
||||||
<para>
|
<listitem><para>
|
||||||
It is also worth noting that <filename>devshell</filename> still works over
|
It is also worth noting that <filename>devshell</filename> still works over
|
||||||
X11 forwarding and similar situations.
|
X11 forwarding and similar situations.
|
||||||
</para>
|
</para></listitem>
|
||||||
|
</itemizedlist>
|
||||||
</note>
|
</note>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue