diff options
Diffstat (limited to 'documentation/sdk-manual/sdk-using.xml')
| -rw-r--r-- | documentation/sdk-manual/sdk-using.xml | 82 |
1 files changed, 41 insertions, 41 deletions
diff --git a/documentation/sdk-manual/sdk-using.xml b/documentation/sdk-manual/sdk-using.xml index 7281e83ef5d..dd220c340b9 100644 --- a/documentation/sdk-manual/sdk-using.xml +++ b/documentation/sdk-manual/sdk-using.xml @@ -19,9 +19,9 @@ <para> You can use a standard SDK to work on Makefile, Autotools, and - Eclipse-based projects. + <trademark class='trade'>Eclipse</trademark>-based projects. See the - "<link linkend='sdk-working-projects'>Working with Different Types of Projects</link>" + "<link linkend='sdk-working-projects'>Using the SDK Toolchain Directly</link>" chapter for more information. </para> @@ -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> @@ -86,14 +86,15 @@ i686 or x86_64. - <replaceable>image_type</replaceable> is the image for which the SDK was built. + <replaceable>image_type</replaceable> is the image for which the SDK was built: + + core-image-minimal or core-image-sato. <replaceable>arch</replaceable> is a string representing the tuned target architecture: - i586, x86_64, powerpc, mips, armv7a or armv5te + 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: + <replaceable>release_version</replaceable> is a string representing the release number of the Yocto Project: &DISTRO;, &DISTRO;+snapshot </literallayout> @@ -120,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. @@ -172,12 +171,11 @@ <para> Once you have the SDK installed, you must run the SDK environment - setup script before you can actually use it. + setup script before you can actually use the SDK. This setup script resides in the directory you chose when you - installed the SDK. - For information on where this setup script can reside, see the - "<link linkend='sdk-appendix-obtain'>Obtaining the SDK</link>" - Appendix. + installed the SDK, which is either the default + <filename>/opt/poky/&DISTRO;</filename> directory or the directory + you chose during installation. </para> <para> @@ -186,9 +184,11 @@ Environment setup scripts begin with the string "<filename>environment-setup</filename>" and include as part of their name the tuned target architecture. - For example, the command to source a setup script for an IA-based - target machine using i586 tuning and located in the default SDK - installation directory is as follows: + As an example, the following commands set the working directory + to where the SDK was installed and then source the environment + setup script. + In this example, the setup script is for an IA-based + target machine using i586 tuning: <literallayout class='monospaced'> $ source /opt/poky/&DISTRO;/environment-setup-i586-poky-linux </literallayout> |