sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

ref-manual, adt-manual: Minor edits from review. 

Fixed some wordings in the ADT manual to remove "Intel-based"
so as not to be biased.

Added "x86" to qualify the types of systems in the toolchain
examples.

Added minor wording to the IMAGE_TYPES variable.

Changed some wording for the IPK_FEED_URIS varilable.

(From yocto-docs rev: 1fa7e0000591bec7e3d0b682df02b95dbee3d4f1)

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 2013-08-14 10:44:38 +03:00 committed by Richard Purdie
parent e7ed0d5e4f
commit d265515478
2 changed files with 13 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
documentation/adt-manual/adt-prepare.xml
View File

@ -253,9 +253,9 @@
<para>Go into that folder and download the toolchain
installer whose name includes the appropriate target
architecture.
For example, if your host development system is an
Intel-based 64-bit system and you are going to use
your cross-toolchain for an Intel-based 32-bit
For example, if your host development system is a
64-bit x86 system and you are going to use
your cross-toolchain for a 32-bit x86
target, go into the <filename>x86_64</filename>
folder and download the following installer:
<literallayout class='monospaced'>
@ -263,7 +263,7 @@
</literallayout></para></listitem>
<listitem><para>Build your own toolchain installer.
For cases where you cannot use an installer
from the download area, you can build your as
from the download area, you can build your own as
described in the
"<link linkend='optionally-building-a-toolchain-installer'>Optionally Building a Toolchain Installer</link>"
section.</para></listitem>
@ -273,8 +273,8 @@
You must change the permissions on the toolchain installer
script so that it is executable.</para>
<para>The following command shows how to run the installer
given a toolchain tarball for a 64-bit development host
system and a 32-bit target architecture.
given a toolchain tarball for a 64-bit x86 development host
system and a 32-bit x86 target architecture.
The example assumes the toolchain installer is located
in <filename>~/Downloads/</filename>.
<literallayout class='monospaced'>

12
documentation/ref-manual/ref-variables.xml
View File

@ -1935,7 +1935,8 @@ Core layer for images cannot be removed
<glossentry id='var-IMAGE_TYPES'><glossterm>IMAGE_TYPES</glossterm>
<glossdef>
<para>
Specifies the complete list of supported image types:
Specifies the complete list of supported image types
by default:
<literallayout class='monospaced'>
jffs2
sum.jffs2
@ -2168,12 +2169,13 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
<glossentry id='var-IPK_FEED_URIS'><glossterm>IPK_FEED_URIS</glossterm>
<glossdef>
<para>
Helps users set up an additional package feed area on
a server for packages you might want to install on a
target that is running an image.
When the IPK backend is in use and package management
is enabled on the target, you can use this variable to
set up <filename>opkg</filename> in the target image
to point to package feeds on a nominated server.
Once the feed is established, you can perform
installations or upgrades using the package manager
at runtime (e.g. <filename>opkg</filename>).
at runtime.
</para>
</glossdef>
</glossentry>