summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2015-04-27 08:15:56 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-04-28 16:30:46 +0100
commit6e4a1a093661722aeaf5ca132eee5befaae95ff0 (patch)
tree9e89a9188bc290d3220cb74cca429e726b26b180 /documentation
parentae736dbdd140975ba43f06e635b461dbf36a117e (diff)
downloadpoky-6e4a1a093661722aeaf5ca132eee5befaae95ff0.tar.gz
dev-manual; ref-manual: Fixed &dash; issue
Fixes [YOCTO #7386] Apparently the "&dash;" ENTITY used throughout the YP manual set to get literal "-" characters in example commands renders into a unicode that is not a dash. This results in users getting errors if they attempt to cut-and-paste a sample command that uses a "-" character from the manual into a shell. I have universally replaced all the "&dash;" strings in the YP manual set to "-" strings. (From yocto-docs rev: ef6dbf591eee70866f163e3c98454b6145f4fa3a) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/dev-manual/dev-manual-common-tasks.xml126
-rw-r--r--documentation/ref-manual/ref-classes.xml6
2 files changed, 66 insertions, 66 deletions
diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index aeda1febe9..7a28176ce0 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -736,13 +736,13 @@
736 ... 736 ...
737 DESCRIPTION = "A useful utility" 737 DESCRIPTION = "A useful utility"
738 ... 738 ...
739 EXTRA_OECONF = "&dash;&dash;enable-something" 739 EXTRA_OECONF = "--enable-something"
740 ... 740 ...
741 741
742 #### bbappended from meta-anotherlayer #### 742 #### bbappended from meta-anotherlayer ####
743 743
744 DESCRIPTION = "Customized utility" 744 DESCRIPTION = "Customized utility"
745 EXTRA_OECONF += "&dash;&dash;enable-somethingelse" 745 EXTRA_OECONF += "--enable-somethingelse"
746 </literallayout> 746 </literallayout>
747 Ideally, you would tidy up these utilities as 747 Ideally, you would tidy up these utilities as
748 follows: 748 follows:
@@ -750,7 +750,7 @@
750 ... 750 ...
751 DESCRIPTION = "Customized utility" 751 DESCRIPTION = "Customized utility"
752 ... 752 ...
753 EXTRA_OECONF = "&dash;&dash;enable-something &dash;&dash;enable-somethingelse" 753 EXTRA_OECONF = "--enable-something --enable-somethingelse"
754 ... 754 ...
755 </literallayout></para></listitem> 755 </literallayout></para></listitem>
756 </itemizedlist></para></listitem> 756 </itemizedlist></para></listitem>
@@ -2322,7 +2322,7 @@
2322 configure script with the appropriate options.</para> 2322 configure script with the appropriate options.</para>
2323 <para>For the case involving a custom configure 2323 <para>For the case involving a custom configure
2324 script, you would run 2324 script, you would run
2325 <filename>./configure &dash;&dash;help</filename> and look for 2325 <filename>./configure --help</filename> and look for
2326 the options you need to set.</para></listitem> 2326 the options you need to set.</para></listitem>
2327 </itemizedlist> 2327 </itemizedlist>
2328 </para> 2328 </para>
@@ -2345,7 +2345,7 @@
2345 configure script as needed. 2345 configure script as needed.
2346 For reference information on configure options specific to the 2346 For reference information on configure options specific to the
2347 software you are building, you can consult the output of the 2347 software you are building, you can consult the output of the
2348 <filename>./configure &dash;&dash;help</filename> command within 2348 <filename>./configure --help</filename> command within
2349 <filename>${S}</filename> or consult the software's upstream 2349 <filename>${S}</filename> or consult the software's upstream
2350 documentation. 2350 documentation.
2351 </para> 2351 </para>
@@ -3827,7 +3827,7 @@
3827 or by entering the command with a help argument as follows: 3827 or by entering the command with a help argument as follows:
3828 <literallayout class='monospaced'> 3828 <literallayout class='monospaced'>
3829 $ wic -h 3829 $ wic -h
3830 $ wic &dash;&dash;help 3830 $ wic --help
3831 </literallayout> 3831 </literallayout>
3832 </para> 3832 </para>
3833 3833
@@ -3843,7 +3843,7 @@
3843 <para> 3843 <para>
3844 You can also get detailed help on a number of topics 3844 You can also get detailed help on a number of topics
3845 from the help system. 3845 from the help system.
3846 The output of <filename>wic &dash;&dash;help</filename> 3846 The output of <filename>wic --help</filename>
3847 displays a list of available help 3847 displays a list of available help
3848 topics under a "Help topics" heading. 3848 topics under a "Help topics" heading.
3849 You can have the help system display the help text for 3849 You can have the help system display the help text for
@@ -3913,38 +3913,38 @@
3913 your own custom file or use a file from a set of 3913 your own custom file or use a file from a set of
3914 existing files as described by further options. 3914 existing files as described by further options.
3915 3915
3916 -o <replaceable>OUTDIR</replaceable>, &dash;&dash;outdir=<replaceable>OUTDIR</replaceable> 3916 -o <replaceable>OUTDIR</replaceable>, --outdir=<replaceable>OUTDIR</replaceable>
3917 The name of a directory in which to create image. 3917 The name of a directory in which to create image.
3918 3918
3919 -i <replaceable>PROPERTIES_FILE</replaceable>, &dash;&dash;infile=<replaceable>PROPERTIES_FILE</replaceable> 3919 -i <replaceable>PROPERTIES_FILE</replaceable>, --infile=<replaceable>PROPERTIES_FILE</replaceable>
3920 The name of a file containing the values for image 3920 The name of a file containing the values for image
3921 properties as a JSON file. 3921 properties as a JSON file.
3922 3922
3923 -e <replaceable>IMAGE_NAME</replaceable>, &dash;&dash;image-name=<replaceable>IMAGE_NAME</replaceable> 3923 -e <replaceable>IMAGE_NAME</replaceable>, --image-name=<replaceable>IMAGE_NAME</replaceable>
3924 The name of the image from which to use the artifacts 3924 The name of the image from which to use the artifacts
3925 (e.g. <filename>core-image-sato</filename>). 3925 (e.g. <filename>core-image-sato</filename>).
3926 3926
3927 -r <replaceable>ROOTFS_DIR</replaceable>, &dash;&dash;rootfs-dir=<replaceable>ROOTFS_DIR</replaceable> 3927 -r <replaceable>ROOTFS_DIR</replaceable>, --rootfs-dir=<replaceable>ROOTFS_DIR</replaceable>
3928 The path to the <filename>/rootfs</filename> directory to use as the 3928 The path to the <filename>/rootfs</filename> directory to use as the
3929 <filename>.wks</filename> rootfs source. 3929 <filename>.wks</filename> rootfs source.
3930 3930
3931 -b <replaceable>BOOTIMG_DIR</replaceable>, &dash;&dash;bootimg-dir=<replaceable>BOOTIMG_DIR</replaceable> 3931 -b <replaceable>BOOTIMG_DIR</replaceable>, --bootimg-dir=<replaceable>BOOTIMG_DIR</replaceable>
3932 The path to the directory containing the boot artifacts 3932 The path to the directory containing the boot artifacts
3933 (e.g. <filename>/EFI</filename> or <filename>/syslinux</filename>) to use as the <filename>.wks</filename> bootimg 3933 (e.g. <filename>/EFI</filename> or <filename>/syslinux</filename>) to use as the <filename>.wks</filename> bootimg
3934 source. 3934 source.
3935 3935
3936 -k <replaceable>KERNEL_DIR</replaceable>, &dash;&dash;kernel-dir=<replaceable>KERNEL_DIR</replaceable> 3936 -k <replaceable>KERNEL_DIR</replaceable>, --kernel-dir=<replaceable>KERNEL_DIR</replaceable>
3937 The path to the directory containing the kernel to use 3937 The path to the directory containing the kernel to use
3938 in the <filename>.wks</filename> boot image. 3938 in the <filename>.wks</filename> boot image.
3939 3939
3940 -n <replaceable>NATIVE_SYSROOT</replaceable>, &dash;&dash;native-sysroot=<replaceable>NATIVE_SYSROOT</replaceable> 3940 -n <replaceable>NATIVE_SYSROOT</replaceable>, --native-sysroot=<replaceable>NATIVE_SYSROOT</replaceable>
3941 The path to the native sysroot containing the tools to use 3941 The path to the native sysroot containing the tools to use
3942 to build the image. 3942 to build the image.
3943 3943
3944 -s, &dash;&dash;skip-build-check 3944 -s, --skip-build-check
3945 Skips the build check. 3945 Skips the build check.
3946 3946
3947 -D, &dash;&dash;debug 3947 -D, --debug
3948 Output debug information. 3948 Output debug information.
3949 </literallayout> 3949 </literallayout>
3950 <note> 3950 <note>
@@ -4154,13 +4154,13 @@
4154 </literallayout> 4154 </literallayout>
4155 Next, the example modifies the 4155 Next, the example modifies the
4156 <filename>directdisksdb.wks</filename> file and changes all 4156 <filename>directdisksdb.wks</filename> file and changes all
4157 instances of "<filename>&dash;&dash;ondisk sda</filename>" 4157 instances of "<filename>--ondisk sda</filename>"
4158 to "<filename>&dash;&dash;ondisk sdb</filename>". 4158 to "<filename>--ondisk sdb</filename>".
4159 The example changes the following two lines and leaves the 4159 The example changes the following two lines and leaves the
4160 remaining lines untouched: 4160 remaining lines untouched:
4161 <literallayout class='monospaced'> 4161 <literallayout class='monospaced'>
4162 part /boot &dash;&dash;source bootimg-pcbios &dash;&dash;ondisk sdb &dash;&dash;label boot &dash;&dash;active &dash;&dash;align 1024 4162 part /boot --source bootimg-pcbios --ondisk sdb --label boot --active --align 1024
4163 part / &dash;&dash;source rootfs &dash;&dash;ondisk sdb &dash;&dash;fstype=ext3 &dash;&dash;label platform &dash;&dash;align 1024 4163 part / --source rootfs --ondisk sdb --fstype=ext3 --label platform --align 1024
4164 </literallayout> 4164 </literallayout>
4165 Once the lines are changed, the example generates the 4165 Once the lines are changed, the example generates the
4166 <filename>directdisksdb</filename> image. 4166 <filename>directdisksdb</filename> image.
@@ -4247,11 +4247,11 @@
4247 somewhere other than the default 4247 somewhere other than the default
4248 <filename>/var/tmp/wic</filename> directory: 4248 <filename>/var/tmp/wic</filename> directory:
4249 <literallayout class='monospaced'> 4249 <literallayout class='monospaced'>
4250 $ wic create ~/test.wks -o /home/trz/testwic &dash;&dash;rootfs-dir \ 4250 $ wic create ~/test.wks -o /home/trz/testwic --rootfs-dir \
4251 /home/trz/yocto/yocto-image/build/tmp/work/crownbay_noemgd-poky-linux/core-image-minimal/1.0-r0/rootfs \ 4251 /home/trz/yocto/yocto-image/build/tmp/work/crownbay_noemgd-poky-linux/core-image-minimal/1.0-r0/rootfs \
4252 &dash;&dash;bootimg-dir /home/trz/yocto/yocto-image/build/tmp/sysroots/crownbay-noemgd/usr/share \ 4252 --bootimg-dir /home/trz/yocto/yocto-image/build/tmp/sysroots/crownbay-noemgd/usr/share \
4253 &dash;&dash;kernel-dir /home/trz/yocto/yocto-image/build/tmp/sysroots/crownbay-noemgd/usr/src/kernel \ 4253 --kernel-dir /home/trz/yocto/yocto-image/build/tmp/sysroots/crownbay-noemgd/usr/src/kernel \
4254 &dash;&dash;native-sysroot /home/trz/yocto/yocto-image/build/tmp/sysroots/x86_64-linux 4254 --native-sysroot /home/trz/yocto/yocto-image/build/tmp/sysroots/x86_64-linux
4255 4255
4256 Creating image(s)... 4256 Creating image(s)...
4257 4257
@@ -4294,7 +4294,7 @@
4294 partitions. 4294 partitions.
4295 The plugins provide a mechanism for mapping values 4295 The plugins provide a mechanism for mapping values
4296 specified in <filename>.wks</filename> files using the 4296 specified in <filename>.wks</filename> files using the
4297 <filename>&dash;&dash;source</filename> keyword to a 4297 <filename>--source</filename> keyword to a
4298 particular plugin implementation that populates a 4298 particular plugin implementation that populates a
4299 corresponding partition. 4299 corresponding partition.
4300 </para> 4300 </para>
@@ -4323,11 +4323,11 @@
4323 When the <filename>wic</filename> implementation needs 4323 When the <filename>wic</filename> implementation needs
4324 to invoke a partition-specific implementation, it looks 4324 to invoke a partition-specific implementation, it looks
4325 for the plugin that has the same name as the 4325 for the plugin that has the same name as the
4326 <filename>&dash;&dash;source</filename> parameter given to 4326 <filename>--source</filename> parameter given to
4327 that partition. 4327 that partition.
4328 For example, if the partition is set up as follows: 4328 For example, if the partition is set up as follows:
4329 <literallayout class='monospaced'> 4329 <literallayout class='monospaced'>
4330 part /boot &dash;&dash;source bootimg-pcbios ... 4330 part /boot --source bootimg-pcbios ...
4331 </literallayout> 4331 </literallayout>
4332 The methods defined as class members of the plugin 4332 The methods defined as class members of the plugin
4333 having the matching <filename>bootimg-pcbios.name</filename> 4333 having the matching <filename>bootimg-pcbios.name</filename>
@@ -4337,7 +4337,7 @@
4337 <para> 4337 <para>
4338 To be more concrete, here is the plugin definition that 4338 To be more concrete, here is the plugin definition that
4339 matches a 4339 matches a
4340 <filename>&dash;&dash;source bootimg-pcbios</filename> usage, 4340 <filename>--source bootimg-pcbios</filename> usage,
4341 along with an example 4341 along with an example
4342 method called by the <filename>wic</filename> implementation 4342 method called by the <filename>wic</filename> implementation
4343 when it needs to invoke an implementation-specific 4343 when it needs to invoke an implementation-specific
@@ -4359,7 +4359,7 @@
4359 The <filename>SourcePlugin</filename> class defines the 4359 The <filename>SourcePlugin</filename> class defines the
4360 following methods, which is the current set of methods 4360 following methods, which is the current set of methods
4361 that can be implemented or overridden by 4361 that can be implemented or overridden by
4362 <filename>&dash;&dash;source</filename> plugins. 4362 <filename>--source</filename> plugins.
4363 Any methods not implemented by a 4363 Any methods not implemented by a
4364 <filename>SourcePlugin</filename> subclass inherit the 4364 <filename>SourcePlugin</filename> subclass inherit the
4365 implementations present in the 4365 implementations present in the
@@ -4491,13 +4491,13 @@
4491 <para> 4491 <para>
4492 Following are the supported options: 4492 Following are the supported options:
4493 <itemizedlist> 4493 <itemizedlist>
4494 <listitem><para><emphasis><filename>&dash;&dash;size</filename>:</emphasis> 4494 <listitem><para><emphasis><filename>--size</filename>:</emphasis>
4495 The minimum partition size in MBytes. 4495 The minimum partition size in MBytes.
4496 Specify an integer value such as 500. 4496 Specify an integer value such as 500.
4497 Do not append the number with "MB". 4497 Do not append the number with "MB".
4498 You do not need this option if you use 4498 You do not need this option if you use
4499 <filename>&dash;&dash;source</filename>.</para></listitem> 4499 <filename>--source</filename>.</para></listitem>
4500 <listitem><para><emphasis><filename>&dash;&dash;source</filename>:</emphasis> 4500 <listitem><para><emphasis><filename>--source</filename>:</emphasis>
4501 This option is a 4501 This option is a
4502 <filename>wic</filename>-specific option that 4502 <filename>wic</filename>-specific option that
4503 names the source of the data that populates 4503 names the source of the data that populates
@@ -4509,7 +4509,7 @@
4509 "<link linkend='openembedded-kickstart-plugins'>Plugins</link>" 4509 "<link linkend='openembedded-kickstart-plugins'>Plugins</link>"
4510 section.</para> 4510 section.</para>
4511 <para>If you use 4511 <para>If you use
4512 <filename>&dash;&dash;source rootfs</filename>, 4512 <filename>--source rootfs</filename>,
4513 <filename>wic</filename> creates a partition as 4513 <filename>wic</filename> creates a partition as
4514 large as needed and to fill it with the contents of 4514 large as needed and to fill it with the contents of
4515 the root filesystem pointed to by the 4515 the root filesystem pointed to by the
@@ -4519,14 +4519,14 @@
4519 option. 4519 option.
4520 The filesystem type used to create the 4520 The filesystem type used to create the
4521 partition is driven by the value of the 4521 partition is driven by the value of the
4522 <filename>&dash;&dash;fstype</filename> option 4522 <filename>--fstype</filename> option
4523 specified for the partition. 4523 specified for the partition.
4524 See the entry on 4524 See the entry on
4525 <filename>&dash;&dash;fstype</filename> that 4525 <filename>--fstype</filename> that
4526 follows for more information. 4526 follows for more information.
4527 </para> 4527 </para>
4528 <para>If you use 4528 <para>If you use
4529 <filename>&dash;&dash;source <replaceable>plugin-name</replaceable></filename>, 4529 <filename>--source <replaceable>plugin-name</replaceable></filename>,
4530 <filename>wic</filename> creates a partition as 4530 <filename>wic</filename> creates a partition as
4531 large as needed and fills it with the contents of 4531 large as needed and fills it with the contents of
4532 the partition that is generated by the 4532 the partition that is generated by the
@@ -4539,10 +4539,10 @@
4539 filesystem type end up being are dependent 4539 filesystem type end up being are dependent
4540 on the given plugin implementation. 4540 on the given plugin implementation.
4541 </para></listitem> 4541 </para></listitem>
4542 <listitem><para><emphasis><filename>&dash;&dash;ondisk</filename> or <filename>&dash;&dash;ondrive</filename>:</emphasis> 4542 <listitem><para><emphasis><filename>--ondisk</filename> or <filename>--ondrive</filename>:</emphasis>
4543 Forces the partition to be created on a particular 4543 Forces the partition to be created on a particular
4544 disk.</para></listitem> 4544 disk.</para></listitem>
4545 <listitem><para><emphasis><filename>&dash;&dash;fstype</filename>:</emphasis> 4545 <listitem><para><emphasis><filename>--fstype</filename>:</emphasis>
4546 Sets the file system type for the partition. 4546 Sets the file system type for the partition.
4547 Valid values are: 4547 Valid values are:
4548 <itemizedlist> 4548 <itemizedlist>
@@ -4559,7 +4559,7 @@
4559 <listitem><para><filename>swap</filename> 4559 <listitem><para><filename>swap</filename>
4560 </para></listitem> 4560 </para></listitem>
4561 </itemizedlist></para></listitem> 4561 </itemizedlist></para></listitem>
4562 <listitem><para><emphasis><filename>&dash;&dash;fsoptions</filename>:</emphasis> 4562 <listitem><para><emphasis><filename>--fsoptions</filename>:</emphasis>
4563 Specifies a free-form string of options to be 4563 Specifies a free-form string of options to be
4564 used when mounting the filesystem. 4564 used when mounting the filesystem.
4565 This string will be copied into the 4565 This string will be copied into the
@@ -4569,15 +4569,15 @@
4569 If not specified, the default string 4569 If not specified, the default string
4570 is "defaults". 4570 is "defaults".
4571 </para></listitem> 4571 </para></listitem>
4572 <listitem><para><emphasis><filename>&dash;&dash;label label</filename>:</emphasis> 4572 <listitem><para><emphasis><filename>--label label</filename>:</emphasis>
4573 Specifies the label to give to the filesystem to 4573 Specifies the label to give to the filesystem to
4574 be made on the partition. 4574 be made on the partition.
4575 If the given label is already in use by another 4575 If the given label is already in use by another
4576 filesystem, a new label is created for the 4576 filesystem, a new label is created for the
4577 partition.</para></listitem> 4577 partition.</para></listitem>
4578 <listitem><para><emphasis><filename>&dash;&dash;active</filename>:</emphasis> 4578 <listitem><para><emphasis><filename>--active</filename>:</emphasis>
4579 Marks the partition as active.</para></listitem> 4579 Marks the partition as active.</para></listitem>
4580 <listitem><para><emphasis><filename>&dash;&dash;align (in KBytes)</filename>:</emphasis> 4580 <listitem><para><emphasis><filename>--align (in KBytes)</filename>:</emphasis>
4581 This option is a <filename>wic</filename>-specific 4581 This option is a <filename>wic</filename>-specific
4582 option that says to start a partition on an 4582 option that says to start a partition on an
4583 x KBytes boundary.</para></listitem> 4583 x KBytes boundary.</para></listitem>
@@ -4594,17 +4594,17 @@
4594 <note> 4594 <note>
4595 Bootloader functionality and boot partitions are 4595 Bootloader functionality and boot partitions are
4596 implemented by the various 4596 implemented by the various
4597 <filename>&dash;&dash;source</filename> 4597 <filename>--source</filename>
4598 plugins that implement bootloader functionality. 4598 plugins that implement bootloader functionality.
4599 The bootloader command essentially provides a means of 4599 The bootloader command essentially provides a means of
4600 modifying bootloader configuration. 4600 modifying bootloader configuration.
4601 </note> 4601 </note>
4602 <itemizedlist> 4602 <itemizedlist>
4603 <listitem><para><emphasis><filename>&dash;&dash;timeout</filename>:</emphasis> 4603 <listitem><para><emphasis><filename>--timeout</filename>:</emphasis>
4604 Specifies the number of seconds before the 4604 Specifies the number of seconds before the
4605 bootloader times out and boots the default option. 4605 bootloader times out and boots the default option.
4606 </para></listitem> 4606 </para></listitem>
4607 <listitem><para><emphasis><filename>&dash;&dash;append</filename>:</emphasis> 4607 <listitem><para><emphasis><filename>--append</filename>:</emphasis>
4608 Specifies kernel parameters. 4608 Specifies kernel parameters.
4609 These parameters will be added to the syslinux 4609 These parameters will be added to the syslinux
4610 <filename>APPEND</filename> or 4610 <filename>APPEND</filename> or
@@ -6529,7 +6529,7 @@
6529 For this scenario, you need to start the PR Service using 6529 For this scenario, you need to start the PR Service using
6530 the <filename>bitbake-prserv</filename> command: 6530 the <filename>bitbake-prserv</filename> command:
6531 <literallayout class='monospaced'> 6531 <literallayout class='monospaced'>
6532 bitbake-prserv &dash;&dash;host <replaceable>ip</replaceable> &dash;&dash;port <replaceable>port</replaceable> &dash;&dash;start 6532 bitbake-prserv --host <replaceable>ip</replaceable> --port <replaceable>port</replaceable> --start
6533 </literallayout> 6533 </literallayout>
6534 In addition to hand-starting the service, you need to 6534 In addition to hand-starting the service, you need to
6535 update the <filename>local.conf</filename> file of each 6535 update the <filename>local.conf</filename> file of each
@@ -7181,9 +7181,9 @@
7181 Given this example, issue the following commands on the 7181 Given this example, issue the following commands on the
7182 target: 7182 target:
7183 <literallayout class='monospaced'> 7183 <literallayout class='monospaced'>
7184 # smart channel &dash;&dash;add all type=rpm-md baseurl=http://server.name/rpm/all 7184 # smart channel --add all type=rpm-md baseurl=http://server.name/rpm/all
7185 # smart channel &dash;&dash;add i585 type=rpm-md baseurl=http://server.name/rpm/i586 7185 # smart channel --add i585 type=rpm-md baseurl=http://server.name/rpm/i586
7186 # smart channel &dash;&dash;add qemux86 type=rpm-md baseurl=http://server.name/rpm/qemux86 7186 # smart channel --add qemux86 type=rpm-md baseurl=http://server.name/rpm/qemux86
7187 </literallayout> 7187 </literallayout>
7188 Also from the target machine, fetch the repository 7188 Also from the target machine, fetch the repository
7189 information using this command: 7189 information using this command:
@@ -8633,13 +8633,13 @@
8633 Consequently, running the tests on other machine 8633 Consequently, running the tests on other machine
8634 means that you have to move the contents and call 8634 means that you have to move the contents and call
8635 <filename>runexported.py</filename> with 8635 <filename>runexported.py</filename> with
8636 "&dash;&dash;deploy-dir <replaceable>path</replaceable>" as 8636 "--deploy-dir <replaceable>path</replaceable>" as
8637 follows: 8637 follows:
8638 <literallayout class='monospaced'> 8638 <literallayout class='monospaced'>
8639 ./runexported.py &dash;&dash;deploy-dir /new/path/on/this/machine testdata.json 8639 ./runexported.py --deploy-dir /new/path/on/this/machine testdata.json
8640 </literallayout> 8640 </literallayout>
8641 <filename>runexported.py</filename> accepts other arguments 8641 <filename>runexported.py</filename> accepts other arguments
8642 as well as described using <filename>&dash;&dash;help</filename>. 8642 as well as described using <filename>--help</filename>.
8643 </para> 8643 </para>
8644 </section> 8644 </section>
8645 8645
@@ -9099,7 +9099,7 @@
9099 | DEBUG: SITE files ['endian-little', 'bit-32', 'ix86-common', 'common-linux', 'common-glibc', 'i586-linux', 'common'] 9099 | DEBUG: SITE files ['endian-little', 'bit-32', 'ix86-common', 'common-linux', 'common-glibc', 'i586-linux', 'common']
9100 | DEBUG: Executing shell function do_compile 9100 | DEBUG: Executing shell function do_compile
9101 | NOTE: make -j 16 9101 | NOTE: make -j 16
9102 | make &dash;&dash;no-print-directory all-am 9102 | make --no-print-directory all-am
9103 | /bin/mkdir -p include/near 9103 | /bin/mkdir -p include/near
9104 | /bin/mkdir -p include/near 9104 | /bin/mkdir -p include/near
9105 | /bin/mkdir -p include/near 9105 | /bin/mkdir -p include/near
@@ -9140,7 +9140,7 @@
9140 | ln -s /home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/build/build/tmp/work/i586-poky-linux/neard/ 9140 | ln -s /home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/build/build/tmp/work/i586-poky-linux/neard/
9141 0.14-r0/neard-0.14/include/dbus.h include/near/dbus.h 9141 0.14-r0/neard-0.14/include/dbus.h include/near/dbus.h
9142 | ./src/genbuiltin nfctype1 nfctype2 nfctype3 nfctype4 p2p > src/builtin.h 9142 | ./src/genbuiltin nfctype1 nfctype2 nfctype3 nfctype4 p2p > src/builtin.h
9143 | i586-poky-linux-gcc -m32 -march=i586 &dash;&dash;sysroot=/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/ 9143 | i586-poky-linux-gcc -m32 -march=i586 --sysroot=/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/
9144 build/build/tmp/sysroots/qemux86 -DHAVE_CONFIG_H -I. -I./include -I./src -I./gdbus -I/home/pokybuild/ 9144 build/build/tmp/sysroots/qemux86 -DHAVE_CONFIG_H -I. -I./include -I./src -I./gdbus -I/home/pokybuild/
9145 yocto-autobuilder/yocto-slave/nightly-x86/build/build/tmp/sysroots/qemux86/usr/include/glib-2.0 9145 yocto-autobuilder/yocto-slave/nightly-x86/build/build/tmp/sysroots/qemux86/usr/include/glib-2.0
9146 -I/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/build/build/tmp/sysroots/qemux86/usr/ 9146 -I/home/pokybuild/yocto-autobuilder/yocto-slave/nightly-x86/build/build/tmp/sysroots/qemux86/usr/
@@ -9215,7 +9215,7 @@
9215 Here is some abbreviated, sample output with the 9215 Here is some abbreviated, sample output with the
9216 missing dependency clearly visible at the end: 9216 missing dependency clearly visible at the end:
9217 <literallayout class='monospaced'> 9217 <literallayout class='monospaced'>
9218 i586-poky-linux-gcc -m32 -march=i586 &dash;&dash;sysroot=/home/scott-lenovo/...... 9218 i586-poky-linux-gcc -m32 -march=i586 --sysroot=/home/scott-lenovo/......
9219 . 9219 .
9220 . 9220 .
9221 . 9221 .
@@ -9399,14 +9399,14 @@
9399 9399
9400 <para> 9400 <para>
9401 <literallayout class='monospaced'> 9401 <literallayout class='monospaced'>
9402 # opcontrol &dash;&dash;reset 9402 # opcontrol --reset
9403 # opcontrol &dash;&dash;start &dash;&dash;separate=lib &dash;&dash;no-vmlinux -c 5 9403 # opcontrol --start --separate=lib --no-vmlinux -c 5
9404 . 9404 .
9405 . 9405 .
9406 [do whatever is being profiled] 9406 [do whatever is being profiled]
9407 . 9407 .
9408 . 9408 .
9409 # opcontrol &dash;&dash;stop 9409 # opcontrol --stop
9410 $ opreport -cl 9410 $ opreport -cl
9411 </literallayout> 9411 </literallayout>
9412 </para> 9412 </para>
@@ -9419,7 +9419,7 @@
9419 five levels deep. 9419 five levels deep.
9420 <note> 9420 <note>
9421 To profile the kernel, you would specify the 9421 To profile the kernel, you would specify the
9422 <filename>&dash;&dash;vmlinux=/path/to/vmlinux</filename> option. 9422 <filename>--vmlinux=/path/to/vmlinux</filename> option.
9423 The <filename>vmlinux</filename> file is usually in the source directory in the 9423 The <filename>vmlinux</filename> file is usually in the source directory in the
9424 <filename>/boot/</filename> directory and must match the running kernel. 9424 <filename>/boot/</filename> directory and must match the running kernel.
9425 </note> 9425 </note>
@@ -9482,7 +9482,7 @@
9482 With this connection, you just need to run "oprofile-server" on the device. 9482 With this connection, you just need to run "oprofile-server" on the device.
9483 By default, OProfile listens on port 4224. 9483 By default, OProfile listens on port 4224.
9484 <note> 9484 <note>
9485 You can change the port using the <filename>&dash;&dash;port</filename> command-line 9485 You can change the port using the <filename>--port</filename> command-line
9486 option. 9486 option.
9487 </note> 9487 </note>
9488 </para> 9488 </para>
@@ -9572,14 +9572,14 @@
9572 If network access to the target is unavailable, you can generate 9572 If network access to the target is unavailable, you can generate
9573 an archive for processing in <filename>oprofile-viewer</filename> as follows: 9573 an archive for processing in <filename>oprofile-viewer</filename> as follows:
9574 <literallayout class='monospaced'> 9574 <literallayout class='monospaced'>
9575 # opcontrol &dash;&dash;reset 9575 # opcontrol --reset
9576 # opcontrol &dash;&dash;start &dash;&dash;separate=lib &dash;&dash;no-vmlinux -c 5 9576 # opcontrol --start --separate=lib --no-vmlinux -c 5
9577 . 9577 .
9578 . 9578 .
9579 [do whatever is being profiled] 9579 [do whatever is being profiled]
9580 . 9580 .
9581 . 9581 .
9582 # opcontrol &dash;&dash;stop 9582 # opcontrol --stop
9583 # oparchive -o my_archive 9583 # oparchive -o my_archive
9584 </literallayout> 9584 </literallayout>
9585 </para> 9585 </para>
diff --git a/documentation/ref-manual/ref-classes.xml b/documentation/ref-manual/ref-classes.xml
index 3889473b6e..880badda73 100644
--- a/documentation/ref-manual/ref-classes.xml
+++ b/documentation/ref-manual/ref-classes.xml
@@ -116,19 +116,19 @@
116 It's useful to have some idea of how the tasks defined by this class work 116 It's useful to have some idea of how the tasks defined by this class work
117 and what they do behind the scenes. 117 and what they do behind the scenes.
118 <itemizedlist> 118 <itemizedlist>
119 <listitem><para><link linkend='ref-tasks-configure'><filename>do_configure</filename></link> &dash; 119 <listitem><para><link linkend='ref-tasks-configure'><filename>do_configure</filename></link> -
120 Regenerates the 120 Regenerates the
121 configure script (using <filename>autoreconf</filename>) and then launches it 121 configure script (using <filename>autoreconf</filename>) and then launches it
122 with a standard set of arguments used during cross-compilation. 122 with a standard set of arguments used during cross-compilation.
123 You can pass additional parameters to <filename>configure</filename> through the 123 You can pass additional parameters to <filename>configure</filename> through the
124 <filename><link linkend='var-EXTRA_OECONF'>EXTRA_OECONF</link></filename> variable. 124 <filename><link linkend='var-EXTRA_OECONF'>EXTRA_OECONF</link></filename> variable.
125 </para></listitem> 125 </para></listitem>
126 <listitem><para><link linkend='ref-tasks-compile'><filename>do_compile</filename></link> &dash; Runs <filename>make</filename> with 126 <listitem><para><link linkend='ref-tasks-compile'><filename>do_compile</filename></link> - Runs <filename>make</filename> with
127 arguments that specify the compiler and linker. 127 arguments that specify the compiler and linker.
128 You can pass additional arguments through 128 You can pass additional arguments through
129 the <filename><link linkend='var-EXTRA_OEMAKE'>EXTRA_OEMAKE</link></filename> variable. 129 the <filename><link linkend='var-EXTRA_OEMAKE'>EXTRA_OEMAKE</link></filename> variable.
130 </para></listitem> 130 </para></listitem>
131 <listitem><para><link linkend='ref-tasks-install'><filename>do_install</filename></link> &dash; Runs <filename>make install</filename> 131 <listitem><para><link linkend='ref-tasks-install'><filename>do_install</filename></link> - Runs <filename>make install</filename>
132 and passes in 132 and passes in
133 <filename>${</filename><link linkend='var-D'><filename>D</filename></link><filename>}</filename> 133 <filename>${</filename><link linkend='var-D'><filename>D</filename></link><filename>}</filename>
134 as <filename>DESTDIR</filename>. 134 as <filename>DESTDIR</filename>.