From 63a151b8749cddc76f5a056abb93516fff16022e Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Fri, 18 May 2018 11:16:24 -0700 Subject: sdk-manual: Updated the "Installing the Extensible SDK" section. The text had not been updated to include the many architectures now supported in the Index of Releases toolchain directories. I added the list of architectures. Renamed the section to a more appropriate section heading. Verified the example and put in the latest output. (From yocto-docs rev: a567f5101d230ef1fa4428e9c6905e9e23bd5855) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/sdk-manual/sdk-extensible.xml | 63 ++++++++++++++++------------- 1 file changed, 36 insertions(+), 27 deletions(-) (limited to 'documentation/sdk-manual/sdk-extensible.xml') diff --git a/documentation/sdk-manual/sdk-extensible.xml b/documentation/sdk-manual/sdk-extensible.xml index 3a99b3791b..0389cb4448 100644 --- a/documentation/sdk-manual/sdk-extensible.xml +++ b/documentation/sdk-manual/sdk-extensible.xml @@ -54,29 +54,29 @@ -
- Setting Up to Use the Extensible SDK +
+ Installing the Extensible 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, the internal build system, devtool, - 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. + 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. @@ -85,6 +85,7 @@ filename and then is immediately followed by a string representing the target architecture. An extensible SDK has the string "-ext" as part of the name. + Following is the general form: poky-glibc-host_system-image_type-arch-toolchain-ext-release_version.sh @@ -93,14 +94,15 @@ i686 or x86_64. - image_type is the image for which the SDK was built. + image_type is the image for which the SDK was built: + + core-image-sato or core-image-minimal arch 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 - release_version is a string representing the release number of the - Yocto Project: + release_version is a string representing the release number of the Yocto Project: &DISTRO;, &DISTRO;+snapshot @@ -131,9 +133,10 @@ home directory. You can choose to install the extensible SDK in any location when you run the installer. - However, the location you choose needs to be writable for whichever - users need to use the SDK, since files will need to be written - under that directory during the normal course of operation. + 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. @@ -141,28 +144,34 @@ toolchain tarball for a 64-bit x86 development host system and 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-minimal-core2-64-toolchain-ext-&DISTRO;.sh - Poky (Yocto Project Reference Distro) Extensible SDK installer version &DISTRO; - =================================================================================== + $ ./Downloads/poky-glibc-x86_64-core-image-minimal-core2-64-toolchain-ext-2.5.sh + Poky (Yocto Project Reference Distro) Extensible SDK installer version 2.5 + ========================================================================== Enter target directory for SDK (default: ~/poky_sdk): You are about to install the SDK to "/home/scottrif/poky_sdk". Proceed[Y/n]? Y - Extracting SDK......................................................................done + Extracting SDK..............done Setting it up... Extracting buildtools... Preparing build system... + Parsing recipes: 100% |##################################################################| Time: 0:00:52 + Initialising tasks: 100% |###############################################################| Time: 0:00:00 + Checking sstate mirror object availability: 100% |#######################################| Time: 0:00:00 + Loading cache: 100% |####################################################################| Time: 0:00:00 + Initialising tasks: 100% |###############################################################| Time: 0:00:00 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. $ . /home/scottrif/poky_sdk/environment-setup-core2-64-poky-linux +
-- cgit v1.2.3-54-g00ecf