mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-05-30 00:20:08 +00:00
Code Issues Projects Releases Wiki Activity

dev-manual, ref-manual: Replaced ‐‐ with "--"

Browse Source 
Fixes [YOCTO #7386]

Apparently, copying HTML displayed commands that have a
double dash created through "‐‐" in the docbook source
causes some issues in the shell.  I have scrubbed the manual set
to replace any "‐‐" strings with "--".

Reported-by: Paul Eggleton <paul.eggleton@intel.com>
(From yocto-docs rev: e88b813b71d7d6d8acd8a8638f2db71265145b64)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2015-03-04 08:55:54 -08:00
committed by Richard Purdie
parent a889cc011c
commit c504276d26
4 changed files with 92 additions and 92 deletions
Download Patch File Download Diff File Expand all files Collapse all files
documentation/dev-manual/dev-manual-model.xml
+25 -25
View File
@@ -1260,7 +1260,7 @@
<filename>aclocal</filename>,
<filename>autoconf</filename>,
<filename>autoheader</filename>,
<filename>automake &dash;&dash;a</filename>, and
<filename>automake --a</filename>, and
<filename>./configure</filename>.
Click on the "Console" tab beneath your source code to
see the results of reconfiguring your project.
@@ -1978,11 +1978,11 @@
<para>
The easiest way to get help with the
<filename>devtool</filename> command is using the
<filename>&dash;&dash;help</filename> option:
<filename>--help</filename> option:
<literallayout class='monospaced'>
$ devtool &dash;&dash;help
usage: devtool [-h] [&dash;&dash;basepath BASEPATH] [-d] [-q]
[&dash;&dash;color {auto,always,never}]
$ devtool --help
usage: devtool [-h] [--basepath BASEPATH] [-d] [-q]
[--color {auto,always,never}]
{create-workspace,deploy-target,undeploy-target,add,modify,extract,update-recipe,status,build,reset}
...
@@ -2002,32 +2002,32 @@
reset Remove a recipe from your workspace
optional arguments:
-h, &dash;&dash;help show this help message and exit
&dash;&dash;basepath BASEPATH Base directory of SDK / build directory
-d, &dash;&dash;debug Enable debug output
-q, &dash;&dash;quiet Print only errors
&dash;&dash;color {auto,always,never}
-h, --help show this help message and exit
--basepath BASEPATH Base directory of SDK / build directory
-d, --debug Enable debug output
-q, --quiet Print only errors
--color {auto,always,never}
Colorize output
Use devtool &lt;command&gt; &dash;&dash;help to get help on a specific command
Use devtool &lt;command&gt; --help to get help on a specific command
</literallayout>
</para>
<para>
As directed in the general help output, you can get more
syntax on a specific command by providing the command
name and using <filename>&dash;&dash;help</filename>:
name and using <filename>--help</filename>:
<literallayout class='monospaced'>
$ devtool add &dash;&dash;help
usage: devtool add [-h] [&dash;&dash;version VERSION] recipename srctree
$ devtool add --help
usage: devtool add [-h] [--version VERSION] recipename srctree
positional arguments:
recipename Name for new recipe to add
srctree Path to external source tree
optional arguments:
-h, &dash;&dash;help show this help message and exit
&dash;&dash;version VERSION, -V VERSION
-h, --help show this help message and exit
--version VERSION, -V VERSION
</literallayout>
</para>
</section>
@@ -2054,7 +2054,7 @@
</literallayout>
<note>
For complete syntax, use the
<filename>devtool add &dash;&dash;help</filename> command.
<filename>devtool add --help</filename> command.
</note>
</para>
@@ -2112,7 +2112,7 @@
</literallayout>
<note>
For complete syntax, use the
<filename>devtool create-workspace &dash;&dash;help</filename> command.
<filename>devtool create-workspace --help</filename> command.
</note>
</para>
@@ -2162,7 +2162,7 @@
</literallayout>
<note>
For complete syntax, use the
<filename>devtool modify &dash;&dash;help</filename> command.
<filename>devtool modify --help</filename> command.
</note>
</para>
</section>
@@ -2182,7 +2182,7 @@
layer before running the <filename>reset</filename> command.
<note>
For complete syntax, use the
<filename>devtool reset &dash;&dash;help</filename> command.
<filename>devtool reset --help</filename> command.
</note>
</para>
</section>
@@ -2208,7 +2208,7 @@
</literallayout>
<note>
For complete syntax, use the
<filename>devtool update-recipe &dash;&dash;help</filename> command.
<filename>devtool update-recipe --help</filename> command.
</note>
</para>
</section>
@@ -2225,7 +2225,7 @@
</literallayout>
<note>
For complete syntax, use the
<filename>devtool update-recipe &dash;&dash;help</filename> command.
<filename>devtool update-recipe --help</filename> command.
</note>
Building your software using <filename>build</filename> is
identical to using BitBake to build the software.
@@ -2246,7 +2246,7 @@
<filename>user@hostname[:destdir]</filename>.
<note>
For complete syntax, use the
<filename>devtool deploy-target &dash;&dash;help</filename> command.
<filename>devtool deploy-target --help</filename> command.
</note>
</para>
</section>
@@ -2269,7 +2269,7 @@
<filename>user@hostname</filename>.
<note>
For complete syntax, use the
<filename>devtool undeploy-target &dash;&dash;help</filename> command.
<filename>devtool undeploy-target --help</filename> command.
</note>
</para>
</section>
@@ -2330,7 +2330,7 @@
<literallayout class='monospaced'>
$ bitbake -c compile -f <replaceable>package</replaceable>
</literallayout>
The <filename>-f</filename> or <filename>&dash;&dash;force</filename>
The <filename>-f</filename> or <filename>--force</filename>
option forces the specified task to execute.
If you find problems with your code, you can just keep editing and
re-testing iteratively until things work as expected.