diff --git a/documentation/sdk-manual/sdk-using.xml b/documentation/sdk-manual/sdk-using.xml index c90620e8dc..c7046d63a7 100644 --- a/documentation/sdk-manual/sdk-using.xml +++ b/documentation/sdk-manual/sdk-using.xml @@ -53,24 +53,24 @@ Installing the SDK - The first thing you need to do is install the SDK on your host - development machine by running the *.sh - installation script. + The first thing you need to do is install the SDK on your + Build Host + by running the *.sh installation script. You can download a tarball installer, which includes the pre-built toolchain, the runqemu - script, and support files from the appropriate directory under - . - Toolchains are available for 32-bit and 64-bit x86 development - systems from the i686 and - x86_64 directories, respectively. + script, and support files from the appropriate + toolchain + directory within the Index of Releases. + Toolchains are available for several 32-bit and 64-bit + architectures with the x86_64 directories, + respectively. The toolchains the Yocto Project provides are based off the - core-image-sato image and contain + core-image-sato and + core-image-minimal images and contain libraries appropriate for developing against that image. - Each type of development system supports five or more target - architectures. @@ -92,7 +92,7 @@ arch 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. release_version is a string representing the release number of the Yocto Project: @@ -121,38 +121,36 @@ The SDK and toolchains are self-contained and by default are - installed into /opt/poky. - However, when you run the SDK installer, you can choose an - installation directory. - - You must change the permissions on the SDK - installer script so that it is executable: - - $ chmod +x poky-glibc-x86_64-core-image-sato-i586-toolchain-&DISTRO;.sh - - + installed into the poky_sdk 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. 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 - ~/Downloads/. + ~/Downloads/ and has execution rights. 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. - $ ./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.