diff options
author | Scott Rifenbark <srifenbark@gmail.com> | 2016-09-21 11:44:43 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-09-28 15:02:32 +0100 |
commit | 959a0620961d5404f826d3545109bb08057fe391 (patch) | |
tree | 6baf56b4e7b2b29ff6a746e2ec058d7af4a24eab /documentation/sdk-manual/sdk-using.xml | |
parent | 4404fc3fe05ad5dd899c1952c1f90f0bb3630f40 (diff) | |
download | poky-959a0620961d5404f826d3545109bb08057fe391.tar.gz |
sdk-manual, dev-manual: Applied SDK review edits.
* Removed the note box formatting for the cross-reference
from the sdk-manual and dev-manual sections that
talk about devtool. The reference is now non-note
form and goes to the ref-manual devtool quick ref.
* Added devtool upgrade as a third item in the list that
introduces methods to use devtool.
* Fixed the working on the devtool finish step 5 for both
the dev-manual and sdk-manual.
* Renamed the new chapter that describes different projects
you can use devtool on. The focus is on using the SDK
toolchain directly.
* Scrubbed the entire sdk-manual for the term "toolchain
installer" and replaced with "SDK installer".
(From yocto-docs rev: 6d4daef49cc6d54a700a8c3965c9e8814f75d20a)
Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/sdk-manual/sdk-using.xml')
-rw-r--r-- | documentation/sdk-manual/sdk-using.xml | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/documentation/sdk-manual/sdk-using.xml b/documentation/sdk-manual/sdk-using.xml index 44cb49c0c8..7281e83ef5 100644 --- a/documentation/sdk-manual/sdk-using.xml +++ b/documentation/sdk-manual/sdk-using.xml | |||
@@ -97,7 +97,7 @@ | |||
97 | 97 | ||
98 | &DISTRO;, &DISTRO;+snapshot | 98 | &DISTRO;, &DISTRO;+snapshot |
99 | </literallayout> | 99 | </literallayout> |
100 | For example, the following toolchain installer is for a 64-bit | 100 | For example, the following SDK installer is for a 64-bit |
101 | development host system and a i586-tuned target architecture | 101 | development host system and a i586-tuned target architecture |
102 | based off the SDK for <filename>core-image-sato</filename> and | 102 | based off the SDK for <filename>core-image-sato</filename> and |
103 | using the current &DISTRO; snapshot: | 103 | using the current &DISTRO; snapshot: |
@@ -106,7 +106,7 @@ | |||
106 | </literallayout> | 106 | </literallayout> |
107 | <note> | 107 | <note> |
108 | As an alternative to downloading an SDK, you can build the | 108 | As an alternative to downloading an SDK, you can build the |
109 | toolchain installer. | 109 | SDK installer. |
110 | For information on building the installer, see the | 110 | For information on building the installer, see the |
111 | "<link linkend='sdk-building-an-sdk-installer'>Building an SDK Installer</link>" | 111 | "<link linkend='sdk-building-an-sdk-installer'>Building an SDK Installer</link>" |
112 | section. | 112 | section. |
@@ -124,7 +124,7 @@ | |||
124 | However, when you run the SDK installer, you can choose an | 124 | However, when you run the SDK installer, you can choose an |
125 | installation directory. | 125 | installation directory. |
126 | <note> | 126 | <note> |
127 | You must change the permissions on the toolchain | 127 | You must change the permissions on the SDK |
128 | installer script so that it is executable: | 128 | installer script so that it is executable: |
129 | <literallayout class='monospaced'> | 129 | <literallayout class='monospaced'> |
130 | $ chmod +x poky-glibc-x86_64-core-image-sato-i586-toolchain-&DISTRO;.sh | 130 | $ chmod +x poky-glibc-x86_64-core-image-sato-i586-toolchain-&DISTRO;.sh |
@@ -136,7 +136,7 @@ | |||
136 | The following command shows how to run the installer given a | 136 | The following command shows how to run the installer given a |
137 | toolchain tarball for a 64-bit x86 development host system and | 137 | toolchain tarball for a 64-bit x86 development host system and |
138 | a 32-bit x86 target architecture. | 138 | a 32-bit x86 target architecture. |
139 | The example assumes the toolchain installer is located in | 139 | The example assumes the SDK installer is located in |
140 | <filename>~/Downloads/</filename>. | 140 | <filename>~/Downloads/</filename>. |
141 | <note> | 141 | <note> |
142 | If you do not have write permissions for the directory | 142 | If you do not have write permissions for the directory |