summaryrefslogtreecommitdiffstats
path: root/documentation/sdk-manual/appendix-obtain.rst
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/sdk-manual/appendix-obtain.rst')
-rw-r--r--documentation/sdk-manual/appendix-obtain.rst14
1 files changed, 7 insertions, 7 deletions
diff --git a/documentation/sdk-manual/appendix-obtain.rst b/documentation/sdk-manual/appendix-obtain.rst
index 7b458f281b..d384b4916a 100644
--- a/documentation/sdk-manual/appendix-obtain.rst
+++ b/documentation/sdk-manual/appendix-obtain.rst
@@ -51,8 +51,8 @@ Follow these steps to locate and hand-install the toolchain:
51 51
52 poky-glibc-x86_64-core-image-sato-core2-64-qemux86-64-toolchain-&DISTRO;.sh 52 poky-glibc-x86_64-core-image-sato-core2-64-qemux86-64-toolchain-&DISTRO;.sh
53 53
544. *Run the Installer:* Be sure you have execution privileges and run 54#. *Run the Installer:* Be sure you have execution privileges and run
55 the installer. Following is an example from the ``Downloads`` 55 the installer. Here is an example from the ``Downloads``
56 directory:: 56 directory::
57 57
58 $ ~/Downloads/poky-glibc-x86_64-core-image-sato-core2-64-qemux86-64-toolchain-&DISTRO;.sh 58 $ ~/Downloads/poky-glibc-x86_64-core-image-sato-core2-64-qemux86-64-toolchain-&DISTRO;.sh
@@ -155,12 +155,12 @@ build the SDK installer. Follow these steps:
155 variable inside your ``local.conf`` file before building the 155 variable inside your ``local.conf`` file before building the
156 SDK installer. Doing so ensures that the eventual SDK 156 SDK installer. Doing so ensures that the eventual SDK
157 installation process installs the appropriate library packages 157 installation process installs the appropriate library packages
158 as part of the SDK. Following is an example using ``libc`` 158 as part of the SDK. Here is an example using ``libc``
159 static development libraries: TOOLCHAIN_TARGET_TASK:append = " 159 static development libraries: TOOLCHAIN_TARGET_TASK:append = "
160 libc-staticdev" 160 libc-staticdev"
161 161
1627. *Run the Installer:* You can now run the SDK installer from 162#. *Run the Installer:* You can now run the SDK installer from
163 ``tmp/deploy/sdk`` in the Build Directory. Following is an example:: 163 ``tmp/deploy/sdk`` in the :term:`Build Directory`. Here is an example::
164 164
165 $ cd poky/build/tmp/deploy/sdk 165 $ cd poky/build/tmp/deploy/sdk
166 $ ./poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-&DISTRO;.sh 166 $ ./poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-&DISTRO;.sh
@@ -225,7 +225,7 @@ Follow these steps to extract the root filesystem:
225 This script is located in the top-level directory in which you 225 This script is located in the top-level directory in which you
226 installed the toolchain (e.g. ``poky_sdk``). 226 installed the toolchain (e.g. ``poky_sdk``).
227 227
228 Following is an example based on the toolchain installed in the 228 Here is an example based on the toolchain installed in the
229 ":ref:`sdk-manual/appendix-obtain:locating pre-built sdk installers`" section:: 229 ":ref:`sdk-manual/appendix-obtain:locating pre-built sdk installers`" section::
230 230
231 $ source poky_sdk/environment-setup-core2-64-poky-linux 231 $ source poky_sdk/environment-setup-core2-64-poky-linux
@@ -233,7 +233,7 @@ Follow these steps to extract the root filesystem:
2333. *Extract the Root Filesystem:* Use the ``runqemu-extract-sdk`` 2333. *Extract the Root Filesystem:* Use the ``runqemu-extract-sdk``
234 command and provide the root filesystem image. 234 command and provide the root filesystem image.
235 235
236 Following is an example command that extracts the root filesystem 236 Here is an example command that extracts the root filesystem
237 from a previously built root filesystem image that was downloaded 237 from a previously built root filesystem image that was downloaded
238 from the :yocto_dl:`Index of Releases </releases/yocto/yocto-&DISTRO;/machines/>`. 238 from the :yocto_dl:`Index of Releases </releases/yocto/yocto-&DISTRO;/machines/>`.
239 This command extracts the root filesystem into the ``core2-64-sato`` 239 This command extracts the root filesystem into the ``core2-64-sato``