diff options
Diffstat (limited to 'documentation/sdk-manual/appendix-obtain.rst')
-rw-r--r-- | documentation/sdk-manual/appendix-obtain.rst | 30 |
1 files changed, 10 insertions, 20 deletions
diff --git a/documentation/sdk-manual/appendix-obtain.rst b/documentation/sdk-manual/appendix-obtain.rst index 3c1dc52d19..0ce828aa29 100644 --- a/documentation/sdk-manual/appendix-obtain.rst +++ b/documentation/sdk-manual/appendix-obtain.rst | |||
@@ -25,8 +25,7 @@ Follow these steps to locate and hand-install the toolchain: | |||
25 | download the installer appropriate for your build host, target | 25 | download the installer appropriate for your build host, target |
26 | hardware, and image type. | 26 | hardware, and image type. |
27 | 27 | ||
28 | The installer files (``*.sh``) follow this naming convention: | 28 | The installer files (``*.sh``) follow this naming convention:: |
29 | :: | ||
30 | 29 | ||
31 | poky-glibc-host_system-core-image-type-arch-toolchain[-ext]-release.sh | 30 | poky-glibc-host_system-core-image-type-arch-toolchain[-ext]-release.sh |
32 | 31 | ||
@@ -55,15 +54,13 @@ Follow these steps to locate and hand-install the toolchain: | |||
55 | 54 | ||
56 | For example, if your build host is a 64-bit x86 system and you need | 55 | For example, if your build host is a 64-bit x86 system and you need |
57 | an extended SDK for a 64-bit core2 target, go into the ``x86_64`` | 56 | an extended SDK for a 64-bit core2 target, go into the ``x86_64`` |
58 | folder and download the following installer: | 57 | folder and download the following installer:: |
59 | :: | ||
60 | 58 | ||
61 | poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-&DISTRO;.sh | 59 | poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-&DISTRO;.sh |
62 | 60 | ||
63 | 4. *Run the Installer:* Be sure you have execution privileges and run | 61 | 4. *Run the Installer:* Be sure you have execution privileges and run |
64 | the installer. Following is an example from the ``Downloads`` | 62 | the installer. Following is an example from the ``Downloads`` |
65 | directory: | 63 | directory:: |
66 | :: | ||
67 | 64 | ||
68 | $ ~/Downloads/poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-&DISTRO;.sh | 65 | $ ~/Downloads/poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-&DISTRO;.sh |
69 | 66 | ||
@@ -132,8 +129,7 @@ build the SDK installer. Follow these steps: | |||
132 | using to build the installer. If | 129 | using to build the installer. If |
133 | SDKMACHINE | 130 | SDKMACHINE |
134 | is not set appropriately, the build fails and provides an error | 131 | is not set appropriately, the build fails and provides an error |
135 | message similar to the following: | 132 | message similar to the following:: |
136 | :: | ||
137 | 133 | ||
138 | The extensible SDK can currently only be built for the same architecture as the machine being built on - SDK_ARCH is | 134 | The extensible SDK can currently only be built for the same architecture as the machine being built on - SDK_ARCH is |
139 | set to i686 (likely via setting SDKMACHINE) which is different from the architecture of the build machine (x86_64). | 135 | set to i686 (likely via setting SDKMACHINE) which is different from the architecture of the build machine (x86_64). |
@@ -144,8 +140,7 @@ build the SDK installer. Follow these steps: | |||
144 | SDK and populate the SDK image, use the following command form. Be | 140 | SDK and populate the SDK image, use the following command form. Be |
145 | sure to replace image with an image (e.g. "core-image-sato"): $ | 141 | sure to replace image with an image (e.g. "core-image-sato"): $ |
146 | bitbake image -c populate_sdk You can do the same for the extensible | 142 | bitbake image -c populate_sdk You can do the same for the extensible |
147 | SDK using this command form: | 143 | SDK using this command form:: |
148 | :: | ||
149 | 144 | ||
150 | $ bitbake image -c populate_sdk_ext | 145 | $ bitbake image -c populate_sdk_ext |
151 | 146 | ||
@@ -170,8 +165,7 @@ build the SDK installer. Follow these steps: | |||
170 | libc-staticdev" | 165 | libc-staticdev" |
171 | 166 | ||
172 | 7. *Run the Installer:* You can now run the SDK installer from | 167 | 7. *Run the Installer:* You can now run the SDK installer from |
173 | ``tmp/deploy/sdk`` in the Build Directory. Following is an example: | 168 | ``tmp/deploy/sdk`` in the Build Directory. Following is an example:: |
174 | :: | ||
175 | 169 | ||
176 | $ cd poky/build/tmp/deploy/sdk | 170 | $ cd poky/build/tmp/deploy/sdk |
177 | $ ./poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-&DISTRO;.sh | 171 | $ ./poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-&DISTRO;.sh |
@@ -211,8 +205,7 @@ Follow these steps to extract the root filesystem: | |||
211 | which you can use with QEMU directly. | 205 | which you can use with QEMU directly. |
212 | 206 | ||
213 | The pre-built root filesystem image files follow these naming | 207 | The pre-built root filesystem image files follow these naming |
214 | conventions: | 208 | conventions:: |
215 | :: | ||
216 | 209 | ||
217 | core-image-profile-arch.tar.bz2 | 210 | core-image-profile-arch.tar.bz2 |
218 | 211 | ||
@@ -233,8 +226,7 @@ Follow these steps to extract the root filesystem: | |||
233 | 226 | ||
234 | For example, if you plan on using a BeagleBone device as your target | 227 | For example, if you plan on using a BeagleBone device as your target |
235 | hardware and your image is a ``core-image-sato-sdk`` image, you can | 228 | hardware and your image is a ``core-image-sato-sdk`` image, you can |
236 | download the following file: | 229 | download the following file:: |
237 | :: | ||
238 | 230 | ||
239 | core-image-sato-sdk-beaglebone-yocto.tar.bz2 | 231 | core-image-sato-sdk-beaglebone-yocto.tar.bz2 |
240 | 232 | ||
@@ -246,8 +238,7 @@ Follow these steps to extract the root filesystem: | |||
246 | installed the toolchain (e.g. ``poky_sdk``). | 238 | installed the toolchain (e.g. ``poky_sdk``). |
247 | 239 | ||
248 | Following is an example based on the toolchain installed in the | 240 | Following is an example based on the toolchain installed in the |
249 | ":ref:`sdk-manual/appendix-obtain:locating pre-built sdk installers`" section: | 241 | ":ref:`sdk-manual/appendix-obtain:locating pre-built sdk installers`" section:: |
250 | :: | ||
251 | 242 | ||
252 | $ source poky_sdk/environment-setup-core2-64-poky-linux | 243 | $ source poky_sdk/environment-setup-core2-64-poky-linux |
253 | 244 | ||
@@ -258,8 +249,7 @@ Follow these steps to extract the root filesystem: | |||
258 | from a previously built root filesystem image that was downloaded | 249 | from a previously built root filesystem image that was downloaded |
259 | from the :yocto_dl:`Index of Releases </releases/yocto/yocto-&DISTRO;/machines/>`. | 250 | from the :yocto_dl:`Index of Releases </releases/yocto/yocto-&DISTRO;/machines/>`. |
260 | This command extracts the root filesystem into the ``core2-64-sato`` | 251 | This command extracts the root filesystem into the ``core2-64-sato`` |
261 | directory: | 252 | directory:: |
262 | :: | ||
263 | 253 | ||
264 | $ runqemu-extract-sdk ~/Downloads/core-image-sato-sdk-beaglebone-yocto.tar.bz2 ~/beaglebone-sato | 254 | $ runqemu-extract-sdk ~/Downloads/core-image-sato-sdk-beaglebone-yocto.tar.bz2 ~/beaglebone-sato |
265 | 255 | ||