summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <srifenbark@gmail.com>2018-06-21 11:37:29 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2018-06-28 09:22:57 +0100
commit293183961e3cf91bb7fd7995e8b1877d961f8d7b (patch)
tree56ce7a1deb93c41ba6daf16e5d7121c50cdd4a76 /documentation
parent3658816dec0f4d3b3e1b1b75cbebb279a43fe97b (diff)
downloadpoky-293183961e3cf91bb7fd7995e8b1877d961f8d7b.tar.gz
sdk-manual: Updates to "Building an SDK Installer" section.
Updated some links. Also, rewrote the note about the libraries. It was inaccurate. (From yocto-docs rev: a0fce0ed36f3d0668e2d211433e7d93fb8833319) 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.xml23
1 files changed, 12 insertions, 11 deletions
diff --git a/documentation/sdk-manual/sdk-appendix-obtain.xml b/documentation/sdk-manual/sdk-appendix-obtain.xml
index ee250de49f..3528c00585 100644
--- a/documentation/sdk-manual/sdk-appendix-obtain.xml
+++ b/documentation/sdk-manual/sdk-appendix-obtain.xml
@@ -98,7 +98,7 @@
98 <title>Building an SDK Installer</title> 98 <title>Building an SDK Installer</title>
99 99
100 <para> 100 <para>
101 As an alternative to locating and downloading a SDK installer, 101 As an alternative to locating and downloading an SDK installer,
102 you can build the SDK installer. 102 you can build the SDK installer.
103 Follow these steps: 103 Follow these steps:
104 <orderedlist> 104 <orderedlist>
@@ -139,8 +139,7 @@
139 Among other things, the script creates the 139 Among other things, the script creates the
140 <ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink>, 140 <ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink>,
141 which is <filename>build</filename> in this case 141 which is <filename>build</filename> in this case
142 and is located in the 142 and is located in the Source Directory.
143 <ulink url='&YOCTO_DOCS_REF_URL;#source-directory'>Source Directory</ulink>.
144 After the script runs, your current working directory 143 After the script runs, your current working directory
145 is set to the <filename>build</filename> directory. 144 is set to the <filename>build</filename> directory.
146 </para></listitem> 145 </para></listitem>
@@ -149,14 +148,14 @@
149 Check to be sure that your 148 Check to be sure that your
150 <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink> 149 <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink>
151 variable in the <filename>local.conf</filename> file in your 150 variable in the <filename>local.conf</filename> file in your
152 <ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink> 151 Build Directory matches the architecture for which you are
153 matches the architecture for which you are building. 152 building.
154 </para></listitem> 153 </para></listitem>
155 <listitem><para> 154 <listitem><para>
156 <emphasis>Make Sure Your SDK Machine is Correctly Set:</emphasis> 155 <emphasis>Make Sure Your SDK Machine is Correctly Set:</emphasis>
157 If you are building a toolchain designed to run on an 156 If you are building a toolchain designed to run on an
158 architecture that differs from your current development host 157 architecture that differs from your current development host
159 machine (i.e. the build machine), be sure that the 158 machine (i.e. the build host), be sure that the
160 <ulink url='&YOCTO_DOCS_REF_URL;#var-SDKMACHINE'><filename>SDKMACHINE</filename></ulink> 159 <ulink url='&YOCTO_DOCS_REF_URL;#var-SDKMACHINE'><filename>SDKMACHINE</filename></ulink>
161 variable in the <filename>local.conf</filename> file in your 160 variable in the <filename>local.conf</filename> file in your
162 Build Directory is correctly set. 161 Build Directory is correctly set.
@@ -175,7 +174,7 @@
175 <literallayout class='monospaced'> 174 <literallayout class='monospaced'>
176 $ bitbake <replaceable>image</replaceable> -c populate_sdk_ext 175 $ bitbake <replaceable>image</replaceable> -c populate_sdk_ext
177 </literallayout> 176 </literallayout>
178 These commands result in a SDK installer that contains the 177 These commands produce an SDK installer that contains the
179 sysroot that matches your target root filesystem.</para> 178 sysroot that matches your target root filesystem.</para>
180 179
181 <para>When the <filename>bitbake</filename> command completes, 180 <para>When the <filename>bitbake</filename> command completes,
@@ -184,16 +183,18 @@
184 <note><title>Notes</title> 183 <note><title>Notes</title>
185 <itemizedlist> 184 <itemizedlist>
186 <listitem><para> 185 <listitem><para>
187 By default, this toolchain does not build static 186 By default, the previous BitBake command does not
188 binaries. 187 build static binaries.
189 If you want to use the toolchain to build these 188 If you want to use the toolchain to build these
190 types of libraries, you need to be sure your SDK 189 types of libraries, you need to be sure your SDK
191 has the appropriate static development libraries. 190 has the appropriate static development libraries.
192 Use the 191 Use the
193 <ulink url='&YOCTO_DOCS_REF_URL;#var-TOOLCHAIN_TARGET_TASK'><filename>TOOLCHAIN_TARGET_TASK</filename></ulink> 192 <ulink url='&YOCTO_DOCS_REF_URL;#var-TOOLCHAIN_TARGET_TASK'><filename>TOOLCHAIN_TARGET_TASK</filename></ulink>
194 variable inside your <filename>local.conf</filename> 193 variable inside your <filename>local.conf</filename>
195 file to install the appropriate library packages 194 file before building the SDK installer.
196 in the SDK. 195 Doing so ensures that the eventual SDK installation
196 process installs the appropriate library packages
197 as part of the SDK.
197 Following is an example using 198 Following is an example using
198 <filename>libc</filename> static development 199 <filename>libc</filename> static development
199 libraries: 200 libraries: