summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorRobert P. J. Day <rpjday@crashcourse.ca>2020-05-06 18:30:20 -0400
committerRichard Purdie <richard.purdie@linuxfoundation.org>2020-05-21 12:40:17 +0100
commit647c13d4ae746a1bb9bd76ff318477dadb4d292f (patch)
tree4a62d7421e2d25ee3f3652ef67c9144a7503dcce /doc
parent5dbee3628972d521d44bdfb282ecc44fc956bdb1 (diff)
downloadbitbake-647c13d4ae746a1bb9bd76ff318477dadb4d292f.tar.gz
user manual: properly tag content as <replaceable>
Tag a couple fields as replaceable to be consistent with rest of manual. Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'doc')
-rw-r--r--doc/bitbake-user-manual/bitbake-user-manual-execution.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/bitbake-user-manual/bitbake-user-manual-execution.xml b/doc/bitbake-user-manual/bitbake-user-manual-execution.xml
index 6c5234ed9..e4251dff5 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-execution.xml
+++ b/doc/bitbake-user-manual/bitbake-user-manual-execution.xml
@@ -618,12 +618,12 @@
<para>
Tasks can be either a shell task or a Python task.
For shell tasks, BitBake writes a shell script to
- <filename>${</filename><link linkend='var-bb-T'><filename>T</filename></link><filename>}/run.do_taskname.pid</filename>
+ <filename>${</filename><link linkend='var-bb-T'><filename>T</filename></link><filename>}/run.do_taskname.<replaceable>pid</replaceable></filename>
and then executes the script.
The generated shell script contains all the exported variables,
and the shell functions with all variables expanded.
Output from the shell script goes to the file
- <filename>${T}/log.do_taskname.pid</filename>.
+ <filename>${T}/log.do_taskname.<replaceable>pid</replaceable></filename>.
Looking at the expanded shell functions in the run file and
the output in the log files is a useful debugging technique.
</para>