summaryrefslogtreecommitdiffstats
path: root/documentation/sdk-manual/sdk-appendix-obtain.xml
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/sdk-manual/sdk-appendix-obtain.xml')
-rw-r--r--documentation/sdk-manual/sdk-appendix-obtain.xml14
1 files changed, 7 insertions, 7 deletions
diff --git a/documentation/sdk-manual/sdk-appendix-obtain.xml b/documentation/sdk-manual/sdk-appendix-obtain.xml
index d7df36f827..3156f77258 100644
--- a/documentation/sdk-manual/sdk-appendix-obtain.xml
+++ b/documentation/sdk-manual/sdk-appendix-obtain.xml
@@ -13,7 +13,7 @@
13 You can use existing, pre-built toolchains by locating and running 13 You can use existing, pre-built toolchains by locating and running
14 an SDK installer script that ships with the Yocto Project. 14 an SDK installer script that ships with the Yocto Project.
15 Using this method, you select and download an architecture-specific 15 Using this method, you select and download an architecture-specific
16 toolchain installer and then run the script to hand-install the 16 SDK installer and then run the script to hand-install the
17 toolchain. 17 toolchain.
18 </para> 18 </para>
19 19
@@ -26,7 +26,7 @@
26 (i.e. <filename>i686</filename> for 32-bit machines or 26 (i.e. <filename>i686</filename> for 32-bit machines or
27 <filename>x86_64</filename> for 64-bit machines).</para> 27 <filename>x86_64</filename> for 64-bit machines).</para>
28 28
29 <para>Go into that folder and download the toolchain installer 29 <para>Go into that folder and download the SDK installer
30 whose name includes the appropriate target architecture. 30 whose name includes the appropriate target architecture.
31 The toolchains provided by the Yocto Project are based off of 31 The toolchains provided by the Yocto Project are based off of
32 the <filename>core-image-sato</filename> image and contain 32 the <filename>core-image-sato</filename> image and contain
@@ -56,8 +56,8 @@
56 <title>Building an SDK Installer</title> 56 <title>Building an SDK Installer</title>
57 57
58 <para> 58 <para>
59 As an alternative to locating and downloading a toolchain installer, 59 As an alternative to locating and downloading a SDK installer,
60 you can build the toolchain installer assuming you have first sourced 60 you can build the SDK installer assuming you have first sourced
61 the environment setup script. 61 the environment setup script.
62 See the 62 See the
63 "<ulink url='&YOCTO_DOCS_QS_URL;#qs-building-images'>Building Images</ulink>" 63 "<ulink url='&YOCTO_DOCS_QS_URL;#qs-building-images'>Building Images</ulink>"
@@ -74,7 +74,7 @@
74 </para> 74 </para>
75 75
76 <para> 76 <para>
77 To build the toolchain installer for a standard SDK and populate 77 To build the SDK installer for a standard SDK and populate
78 the SDK image, use the following command: 78 the SDK image, use the following command:
79 <literallayout class='monospaced'> 79 <literallayout class='monospaced'>
80 $ bitbake <replaceable>image</replaceable> -c populate_sdk 80 $ bitbake <replaceable>image</replaceable> -c populate_sdk
@@ -83,12 +83,12 @@
83 <literallayout class='monospaced'> 83 <literallayout class='monospaced'>
84 $ bitbake <replaceable>image</replaceable> -c populate_sdk_ext 84 $ bitbake <replaceable>image</replaceable> -c populate_sdk_ext
85 </literallayout> 85 </literallayout>
86 These commands result in a toolchain installer that contains the sysroot 86 These commands result in a SDK installer that contains the sysroot
87 that matches your target root filesystem. 87 that matches your target root filesystem.
88 </para> 88 </para>
89 89
90 <para> 90 <para>
91 When the <filename>bitbake</filename> command completes, the toolchain 91 When the <filename>bitbake</filename> command completes, the SDK
92 installer will be in 92 installer will be in
93 <filename>tmp/deploy/sdk</filename> in the Build Directory. 93 <filename>tmp/deploy/sdk</filename> in the Build Directory.
94 <note><title>Notes</title> 94 <note><title>Notes</title>