summaryrefslogtreecommitdiffstats
path: root/documentation/adt-manual
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-08-14 07:44:38 (GMT)
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-08-26 10:06:29 (GMT)
commitd265515478f175c164ee3658792b7776f128b6d9 (patch)
treece23a4fd9a80b6581bbde8f088dc1810578eca80 /documentation/adt-manual
parente7ed0d5e4fc36ea0998c70c2d916012564a315ec (diff)
downloadpoky-d265515478f175c164ee3658792b7776f128b6d9.tar.gz
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>
Diffstat (limited to 'documentation/adt-manual')
-rw-r--r--documentation/adt-manual/adt-prepare.xml12
1 files changed, 6 insertions, 6 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 343b741..54f48a8 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -253,9 +253,9 @@
253 <para>Go into that folder and download the toolchain 253 <para>Go into that folder and download the toolchain
254 installer whose name includes the appropriate target 254 installer whose name includes the appropriate target
255 architecture. 255 architecture.
256 For example, if your host development system is an 256 For example, if your host development system is a
257 Intel-based 64-bit system and you are going to use 257 64-bit x86 system and you are going to use
258 your cross-toolchain for an Intel-based 32-bit 258 your cross-toolchain for a 32-bit x86
259 target, go into the <filename>x86_64</filename> 259 target, go into the <filename>x86_64</filename>
260 folder and download the following installer: 260 folder and download the following installer:
261 <literallayout class='monospaced'> 261 <literallayout class='monospaced'>
@@ -263,7 +263,7 @@
263 </literallayout></para></listitem> 263 </literallayout></para></listitem>
264 <listitem><para>Build your own toolchain installer. 264 <listitem><para>Build your own toolchain installer.
265 For cases where you cannot use an installer 265 For cases where you cannot use an installer
266 from the download area, you can build your as 266 from the download area, you can build your own as
267 described in the 267 described in the
268 "<link linkend='optionally-building-a-toolchain-installer'>Optionally Building a Toolchain Installer</link>" 268 "<link linkend='optionally-building-a-toolchain-installer'>Optionally Building a Toolchain Installer</link>"
269 section.</para></listitem> 269 section.</para></listitem>
@@ -273,8 +273,8 @@
273 You must change the permissions on the toolchain installer 273 You must change the permissions on the toolchain installer
274 script so that it is executable.</para> 274 script so that it is executable.</para>
275 <para>The following command shows how to run the installer 275 <para>The following command shows how to run the installer
276 given a toolchain tarball for a 64-bit development host 276 given a toolchain tarball for a 64-bit x86 development host
277 system and a 32-bit target architecture. 277 system and a 32-bit x86 target architecture.
278 The example assumes the toolchain installer is located 278 The example assumes the toolchain installer is located
279 in <filename>~/Downloads/</filename>. 279 in <filename>~/Downloads/</filename>.
280 <literallayout class='monospaced'> 280 <literallayout class='monospaced'>