mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-02-20 08:29:42 +01:00
Code Issues Packages Projects Releases Wiki Activity

sdk-manual: Edits to standard SDK intro and install sections

Browse Source 
Changed the output to reflect the real command's output.  Updated
prose to match (mostly) that used in the similar extensible SDK
sections.

(From yocto-docs rev: dd929244162eaf00f5e552ea8a96a7c2a89daa9f)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2018-05-31 15:51:35 -07:00
committed by Richard Purdie
parent 3286f68185
commit 7544fbc608
1 changed files with 26 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files

54
documentation/sdk-manual/sdk-using.xml
View File

@@ -53,24 +53,24 @@
<title>Installing the SDK</title>
<para>
The first thing you need to do is install the SDK on your host
development machine by running the <filename>*.sh</filename>
installation script.
The first thing you need to do is install the SDK on your
<ulink url='&YOCTO_DOCS_REF_URL;#hardware-build-system-term'>Build Host</ulink>
by running the <filename>*.sh</filename> installation script.
</para>
<para>
You can download a tarball installer, which includes the
pre-built toolchain, the <filename>runqemu</filename>
script, and support files from the appropriate directory under
<ulink url='&YOCTO_TOOLCHAIN_DL_URL;'></ulink>.
Toolchains are available for 32-bit and 64-bit x86 development
systems from the <filename>i686</filename> and
<filename>x86_64</filename> directories, respectively.
script, and support files from the appropriate
<ulink url='&YOCTO_TOOLCHAIN_DL_URL;'>toolchain</ulink>
directory within the Index of Releases.
Toolchains are available for several 32-bit and 64-bit
architectures with the <filename>x86_64</filename> directories,
respectively.
The toolchains the Yocto Project provides are based off the
<filename>core-image-sato</filename> image and contain
<filename>core-image-sato</filename> and
<filename>core-image-minimal</filename> images and contain
libraries appropriate for developing against that image.
Each type of development system supports five or more target
architectures.
</para>
<para>
@@ -92,7 +92,7 @@
<replaceable>arch</replaceable> is a string representing the tuned target architecture:
aarch64, armv5e, core2-64, coretexah8f-neon, i586, mips32r2, mips64, or ppc7400.
aarch64, armv5e, core2-64, i586, mips32r2, mips64, ppc7400, or cortexa8hf-neon.
<replaceable>release_version</replaceable> is a string representing the release number of the Yocto Project:
@@ -121,38 +121,36 @@
<para>
The SDK and toolchains are self-contained and by default are
installed into <filename>/opt/poky</filename>.
However, when you run the SDK installer, you can choose an
installation directory.
<note>
You must change the permissions on the SDK
installer script so that it is executable:
<literallayout class='monospaced'>
$ chmod +x poky-glibc-x86_64-core-image-sato-i586-toolchain-&DISTRO;.sh
</literallayout>
</note>
installed into the <filename>poky_sdk</filename> folder in your
home directory.
You can choose to install the extensible SDK in any location when
you run the installer.
However, because files need to be written under that directory
during the normal course of operation, the location you choose
for installation must be writable for whichever
users need to use the SDK.
</para>
<para>
The following command shows how to run the installer given a
toolchain tarball for a 64-bit x86 development host system and
a 32-bit x86 target architecture.
a 64-bit x86 target architecture.
The example assumes the SDK installer is located in
<filename>~/Downloads/</filename>.
<filename>~/Downloads/</filename> and has execution rights.
<note>
If you do not have write permissions for the directory
into which you are installing the SDK, the installer
notifies you and exits.
Be sure you have write permissions in the directory and
run the installer again.
For that case, set up the proper permissions in the directory
and run the installer again.
</note>
<literallayout class='monospaced'>
$ ./poky-glibc-x86_64-core-image-sato-i586-toolchain-&DISTRO;.sh
$ ./Downloads/poky-glibc-x86_64-core-image-sato-i586-toolchain-&DISTRO;.sh
Poky (Yocto Project Reference Distro) SDK installer version &DISTRO;
===============================================================
Enter target directory for SDK (default: /opt/poky/&DISTRO;):
You are about to install the SDK to "/opt/poky/&DISTRO;". Proceed[Y/n]? Y
Extracting SDK.......................................................................done
Extracting SDK........................................ ..............................done
Setting it up...done
SDK has been successfully set up and is ready to be used.
Each time you wish to use the SDK in a new shell session, you need to source the environment setup script e.g.