From e901047d4db48fc5e5f20d71fa20601a9e735ab6 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 26 Aug 2013 11:17:49 +0300 Subject: yocto-project-qs, adt-manual: Updates to toolchain installer script The way in which the toolchain installer scripts are named has changed. I have updated two sections that describe this so that the new naming scheme is used. (From yocto-docs rev: 71b70a12c72bca7cad565b5d6f44b2c6b311844d) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/adt-manual/adt-prepare.xml | 17 ++++-- .../yocto-project-qs/yocto-project-qs.xml | 60 ++++++++++++++-------- 2 files changed, 51 insertions(+), 26 deletions(-) (limited to 'documentation') diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml index f8ba557f39..6900b0cd8c 100644 --- a/documentation/adt-manual/adt-prepare.xml +++ b/documentation/adt-manual/adt-prepare.xml @@ -229,8 +229,10 @@ Using a Cross-Toolchain Tarball - If you want to simply install the cross-toolchain by hand, you can + If you want to simply install a cross-toolchain by hand, you can do so by running the toolchain installer. + The installer includes the pre-built cross-toolchain, the + runqemu script, and support files. If you use this method to install the cross-toolchain, you might still need to install the target sysroot by installing and extracting it separately. @@ -241,25 +243,30 @@ Follow these steps: - Get the toolchain installer using one of the + Get your toolchain installer using one of the following methods: Go to and find the folder that matches your host development system (i.e. i686 - for 32-bit machines or x86-64 + for 32-bit machines or x86_64 for 64-bit machines). Go into that folder and download the toolchain installer whose name includes the appropriate target architecture. + The toolchains provided by the Yocto Project + are based off of the + core-image-sato image and + contain libraries appropriate for developing + against that image. For example, if your host development system is a 64-bit x86 system and you are going to use your cross-toolchain for a 32-bit x86 target, go into the x86_64 folder and download the following installer: - poky-eglibc-x86_64-i586-toolchain-&DISTRO;.sh + poky-eglibc-x86_64-core-image-sato-i586.sh Build your own toolchain installer. For cases where you cannot use an installer @@ -278,7 +285,7 @@ The example assumes the toolchain installer is located in ~/Downloads/. - $ ~/Downloads/poky-eglibc-x86_64-i586-toolchain-&DISTRO;.sh + $ ~/Downloads/poky-eglibc-x86_64-core-image-sato-i586.sh If you do not have write permissions for the directory diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml index a8e8c3a35a..372a86efd0 100644 --- a/documentation/yocto-project-qs/yocto-project-qs.xml +++ b/documentation/yocto-project-qs/yocto-project-qs.xml @@ -552,44 +552,62 @@
Installing the Toolchain + - You can download a tarball installer, which includes the pre-built toolchain, the - runqemu + 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. - Each type of development system supports five target architectures. - The names of the tarball installer scripts are such that a string representing the - host system appears first in the filename and then is immediately followed by a - string representing the target architecture. + Toolchains are available for 32-bit and 64-bit x86 development + systems from the i686 and + x86_64 directories, respectively. + The toolchains the Yocto Project provides are based off the + core-image-sato image and contain + libraries appropriate for developing against that image. + Each type of development system supports five or more target + architectures. + + + + The names of the tarball installer scripts are such that a + string representing the host system appears first in the + filename and then is immediately followed by a string + that represents the target architecture. - poky-eglibc-<host_system>-<arch>-toolchain-gmae-<release>.sh + poky-eglibc-<host_system>-<image_type>-<arch>.sh Where: <host_system> is a string representing your development system: i686 or x86_64. - <arch> is a string representing the target architecture: - i586, x86_64, powerpc, mips, or arm. + <image_type> is a string representing the image you wish to + develop a Software Development Toolkit (SDK) for use against. + The Yocto Project builds toolchain installers using the + following BitBake command: + + bitbake core-image-sato -c do_populatesdk core-image-sato - <release> is the version of Yocto Project. + <arch> is a string representing the tuned target architecture: + + i586, x86_64, powerpc, mips, armv7a or armv5te - For example, the following toolchain installer is for a 64-bit development - host system and a 32-bit target architecture: + For example, the following toolchain installer is for a 64-bit + development host system and a i586-tuned target architecture + based off the SDK for core-image-sato: + + poky-eglibc-x86_64-core-image-sato-i586.sh + - - poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.sh - - - Toolchains are self-contained and by default are installed into /opt/poky. - However, when you run the toolchain installer, you can choose an installation directory. + Toolchains are self-contained and by default are installed into + /opt/poky. + However, when you run the toolchain installer, you can choose an + installation directory. @@ -610,7 +628,7 @@ - $ ~/Downloads/poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.sh + $ ~/Downloads/poky-eglibc-x86_64-core-image-sato-i586.sh -- cgit v1.2.3-54-g00ecf