1
0
mirror of https://git.yoctoproject.org/poky synced 2026-06-01 00:59:48 +00:00

sdk-manual: Applied 2nd round of review edits.

(From yocto-docs rev: 046b8ed69e0c6403f455e2ec8a0ccc30aea894de)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2016-03-22 09:49:33 -07:00
committed by Richard Purdie
parent 6db8cbcbad
commit 54050ffceb
3 changed files with 10 additions and 25 deletions
+4 -15
View File
@@ -38,12 +38,6 @@
You can see the directory structure in the
"<link linkend='sdk-installed-standard-sdk-directory-structure'>Installed Standard SDK Directory Structure</link>"
section.
<note>
You can also find information on how the Yocto Project
OpenEmbedded build system creates an SDK image by looking at the
"<ulink url='&YOCTO_DOCS_REF_URL;#sdk-generation-dev-environment'>SDK Generation</ulink>"
section in the Yocto Project Reference Manual.
</note>
</para>
</section>
@@ -84,12 +78,7 @@
i686 or x86_64.
<replaceable>image_type</replaceable> is a string representing the image you wish to
develop a SDK for use against. The Yocto Project builds
installers for standard SDKs using the following BitBake
command:
bitbake core-image-sato -c populate_sdk
<replaceable>image_type</replaceable> is the image for which the SDK was built.
<replaceable>arch</replaceable> is a string representing the tuned target architecture:
@@ -116,11 +105,11 @@
installation directory.
<note>
You must change the permissions on the toolchain
installer script so that it is executable.
Here is an example:
installer script so that it is executable:
<literallayout class='monospaced'>
$ chmod +x poky-glibc-x86_64-core-image-sato-i586-toolchain-2.1.sh
$ chmod +x poky-glibc-x86_64-core-image-sato-i586-toolchain-2.1.sh
</literallayout>
This example makes the installation script executable.
</note>
</para>