summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2017-07-10 14:05:51 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-07-22 09:19:25 +0100
commit8b04dca4556ef0922c1f649dde05ce83926f8b34 (patch)
treed738cd9bb6248ea22bac562ce60fb96d09768ad0 /documentation
parent5ffec4ad91193b006b35a3e969b6573fe18ad593 (diff)
downloadpoky-8b04dca4556ef0922c1f649dde05ce83926f8b34.tar.gz
sdk-manual: Updated section to locate and install pre-built SDK
The section "Locating Pre-Built SDK Installers" was turned into a procedure. I also added some information on the actual names of the *.sh files. (From yocto-docs rev: 548886d5a392164783596c0c04779aaffd6ac930) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r--documentation/sdk-manual/sdk-appendix-obtain.xml74
1 files changed, 54 insertions, 20 deletions
diff --git a/documentation/sdk-manual/sdk-appendix-obtain.xml b/documentation/sdk-manual/sdk-appendix-obtain.xml
index d0cbf9c85e..3fae8052ac 100644
--- a/documentation/sdk-manual/sdk-appendix-obtain.xml
+++ b/documentation/sdk-manual/sdk-appendix-obtain.xml
@@ -18,37 +18,71 @@
18 </para> 18 </para>
19 19
20 <para> 20 <para>
21 You can find SDK installers here: 21 Follow these steps to locate and hand-install the toolchain:
22 <itemizedlist> 22 <orderedlist>
23 <listitem><para><emphasis>Standard SDK Installers:</emphasis> 23 <listitem><para>
24 <emphasis>Go to the Installers Directory:</emphasis>
24 Go to <ulink url='&YOCTO_TOOLCHAIN_DL_URL;'></ulink> 25 Go to <ulink url='&YOCTO_TOOLCHAIN_DL_URL;'></ulink>
25 and find the folder that matches your host development system 26 </para></listitem>
27 <listitem><para>
28 <emphasis>Open the Folder for Your Development System:</emphasis>
29 Open the folder that matches your host development system
26 (i.e. <filename>i686</filename> for 32-bit machines or 30 (i.e. <filename>i686</filename> for 32-bit machines or
27 <filename>x86_64</filename> for 64-bit machines).</para> 31 <filename>x86_64</filename> for 64-bit machines).
32 </para></listitem>
33 <listitem><para>
34 <emphasis>Locate and Download the SDK Installer:</emphasis>
35 You need to find and download the installer appropriate for
36 your development system, target hardware, and image type.
37 </para>
38
39 <para>The installer files (<filename>*.sh</filename>) follow
40 this naming convention:
41 <literallayout class='monospaced'>
42 poky-eglibc-<replaceable>host_system</replaceable>-core-image-<replaceable>type</replaceable>-<replaceable>arch</replaceable>-toolchain-ext-<replaceable>release</replaceable>.sh
43
44 Where:
45 <replaceable>host_system</replaceable> is a string representing your development system:
46 i686 or x86_64.
47
48 <replaceable>type</replaceable> is a string representing either a "sato" or "minimal"
49 image.
50
51 <replaceable>arch</replaceable> is a string representing the target architecture:
52 aarch64, armv5e, core2-64, coretexa8hf-neon, i586, mips3242,
53 mips64, or ppc7400.
28 54
29 <para>Go into that folder and download the SDK installer 55 <replaceable>release</replaceable> is the version of Yocto Project.
30 whose name includes the appropriate target architecture. 56
57 NOTE:
58 The standard SDK installer does not have the "-ext" string as
59 part of the filename.
60
61 </literallayout>
31 The toolchains provided by the Yocto Project are based off of 62 The toolchains provided by the Yocto Project are based off of
32 the <filename>core-image-sato</filename> image and contain 63 the <filename>core-image-sato</filename> and
33 libraries appropriate for developing against that image. 64 <filename>core-image-minimal</filename> images and contain
34 For example, if your host development system is a 64-bit x86 65 libraries appropriate for developing against those images.
35 system and you are going to use your cross-toolchain for a 66 </para>
36 32-bit x86 target, go into the <filename>x86_64</filename> 67
68 <para>For example, if your host development system is a
69 64-bit x86 system and you are need an extended SDK for a
70 64-bit core2 target, go into the <filename>x86_64</filename>
37 folder and download the following installer: 71 folder and download the following installer:
38 <literallayout class='monospaced'> 72 <literallayout class='monospaced'>
39 poky-glibc-x86_64-core-image-sato-i586-toolchain-&DISTRO;.sh 73 poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-&DISTRO;.sh
40 </literallayout> 74 </literallayout>
41 </para></listitem> 75 </para></listitem>
42 <listitem><para><emphasis>Extensible SDK Installers:</emphasis> 76 <listitem><para>
43 Installers for the extensible SDK are also located in 77 <emphasis>Run the Installer:</emphasis>
44 <ulink url='&YOCTO_TOOLCHAIN_DL_URL;'></ulink>. 78 Be sure you have execution privileges and run the installer.
45 These installers have the string 79 Following is an example from the <filename>Downloads</filename>
46 <filename>ext</filename> as part of their names: 80 directory:
47 <literallayout class='monospaced'> 81 <literallayout class='monospaced'>
48 poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-&DISTRO;.sh 82 $ ~/Downloads/poky-glibc-x86_64-core-image-sato-core2-64-toolchain-ext-&DISTRO;.sh
49 </literallayout> 83 </literallayout>
50 </para></listitem> 84 </para></listitem>
51 </itemizedlist> 85 </orderedlist>
52 </para> 86 </para>
53</section> 87</section>
54 88