From c4a923bcb0194c05b14d40be7ad4ecd193eb7a69 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 13 Sep 2012 14:01:58 -0700 Subject: documentation: Toolchain corrections from tarball to .sh file For 1.3 there is not longer a toolchain tarball. Instead, there is a wrapper script that lets you install the tarball. This fundamental usage model change caused several ripples throughout the documentation set. I have changed wordings and examples to reflect the new paradigm. (From yocto-docs rev: afb2069daa91e04c0f78ba425a6b184cb820d888) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/adt-manual/adt-command.xml | 2 +- documentation/adt-manual/adt-intro.xml | 4 +-- documentation/adt-manual/adt-prepare.xml | 44 ++++++++++++++++++++------------ 3 files changed, 30 insertions(+), 20 deletions(-) (limited to 'documentation/adt-manual') diff --git a/documentation/adt-manual/adt-command.xml b/documentation/adt-manual/adt-command.xml index f5ed906962..074e51c1f1 100644 --- a/documentation/adt-manual/adt-command.xml +++ b/documentation/adt-manual/adt-command.xml @@ -32,7 +32,7 @@ For an Autotools-based project, you can use the cross-toolchain by just passing the appropriate host option to configure.sh. The host option you use is derived from the name of the environment setup - script in /opt/poky resulting from unpacking the + script in /opt/poky resulting from installation of the cross-toolchain tarball. For example, the host option for an ARM-based target that uses the GNU EABI is armv5te-poky-linux-gnueabi. diff --git a/documentation/adt-manual/adt-intro.xml b/documentation/adt-manual/adt-intro.xml index 47e4c3685e..c83880b2d6 100644 --- a/documentation/adt-manual/adt-intro.xml +++ b/documentation/adt-manual/adt-intro.xml @@ -54,8 +54,8 @@ The cross-toolchain consists of a cross-compiler, cross-linker, and cross-debugger that are used to develop user-space applications for targeted hardware. - This toolchain is created either by running the ADT Installer script or - through a build directory that is based on your metadata + This toolchain is created either by running the ADT Installer script, a toolchain installer + script, or through a build directory that is based on your metadata configuration or extension for your targeted device. The cross-toolchain works with a matching target sysroot. diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml index e512c89a1c..0b74505d7e 100644 --- a/documentation/adt-manual/adt-prepare.xml +++ b/documentation/adt-manual/adt-prepare.xml @@ -29,8 +29,7 @@ Avoid mixing installation methods when installing toolchains for different architectures. For example, avoid using the ADT Installer to install some toolchains and then hand-installing - cross-development toolchains from downloaded tarballs to install toolchains - for different architectures. + cross-development toolchains by running the toolchain installer for different architectures. Mixing installation methods can result in situations where the ADT Installer becomes unreliable and might not install the toolchain. If you must mix installation methods, you might avoid problems by deleting @@ -46,9 +45,9 @@ For example, you can configure the installation to install the QEMU emulator and the user-space NFS, specify which root filesystem profiles to download, and define the target sysroot location. - Use an Existing Toolchain Tarball: + Use an Existing Toolchain: Using this method, you select and download an architecture-specific - toolchain tarball and then hand-install the toolchain. + toolchain installer and then run the script to hand-install the toolchain. If you use this method, you just get the cross-toolchain and QEMU - you do not get any of the other mentioned benefits had you run the ADT Installer script. Use the Toolchain from within the Build Directory: @@ -226,8 +225,8 @@ Using a Cross-Toolchain Tarball - If you want to simply install the cross-toolchain by hand, you can do so by using an existing - cross-toolchain tarball. + If you want to simply install the cross-toolchain by hand, you can do so by running the + toolchain installer. If you use this method to install the cross-toolchain and you still need to install the target sysroot, you will have to extract and install sysroot separately. For information on how to do this, see the @@ -242,30 +241,41 @@ and find the folder that matches your host development system (i.e. i686 for 32-bit machines or x86-64 for 64-bit machines). - Go into that folder and download the toolchain tarball whose name + Go into that folder and download the toolchain installer whose name includes the appropriate target architecture. For example, if your host development system is an Intel-based 64-bit system and you are going to use your cross-toolchain for an Intel-based 32-bit target, go into the - x86_64 folder and download the following tarball: + x86_64 folder and download the following installer: - poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.tar.bz2 + poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.sh - As an alternative to steps one and two, you can build the toolchain tarball + As an alternative to steps one and two, you can build the toolchain installer if you have a build directory. If you need GMAE, you should use the bitbake meta-toolchain-gmae command. - The resulting tarball will support such development. + The resulting installation script when run will support such development. However, if you are not concerned with GMAE, - you can generate the tarball using bitbake meta-toolchain. + you can generate the toolchain installer using + bitbake meta-toolchain. Use the appropriate bitbake command only after you have sourced the oe-build-init-env script located in the source directory. - When the bitbake command completes, the tarball will + When the bitbake command completes, the toolchain installer will be in tmp/deploy/sdk in the build directory. - - Make sure you are in the root directory with root privileges and then expand - the tarball. - The tarball expands into &YOCTO_ADTPATH_DIR;. + + + Once you have the installer, run it to install the toolchain. + The following command shows how to run the installer given a toolchain tarball + for a 64-bit development host system and a 32-bit target architecture. + The example assumes the toolchain installer is located in ~/Downloads/. + + $ ~/Downloads/poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.sh + + + If you do not have write permissions for the directory into which you are installing + the toolchain, the toolchain installer notifies you and exits. + Be sure you have write permissions in the directory and run the installer again. + Once the tarball is expanded, the cross-toolchain is installed. You will notice environment setup files for the cross-toolchain in the directory. -- cgit v1.2.3-54-g00ecf