From 257dbe8d39a6b530abc883086024604a0bd59b64 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 19 Jan 2012 12:52:27 -0600 Subject: documentation/adt-manual/adt-prepare.xml: Updates for 1.1.1 These changes reflect working through the chapter using the 1.1.1 release. Several areas needed tweaking. (From yocto-docs rev: 566b8a492e502e88a1404f833db140a6408da592) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/adt-manual/adt-prepare.xml | 50 +++++++++++++++++--------------- 1 file changed, 27 insertions(+), 23 deletions(-) (limited to 'documentation') diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml index b45da5f6c2..79c44849e9 100644 --- a/documentation/adt-manual/adt-prepare.xml +++ b/documentation/adt-manual/adt-prepare.xml @@ -100,7 +100,7 @@ a top-level directory named adt-installer: $ cd ~ - $ cp ~/poky/build/tmp/deploy/sdk/adt_installer.tar.bz2 $HOME + $ cp ~/yocto-project/build/tmp/deploy/sdk/adt_installer.tar.bz2 $HOME $ tar -xjf adt_installer.tar.bz2 Unpacking it creates the directory adt-installer, @@ -165,9 +165,10 @@ After you have configured the adt_installer.conf file, - run the installer using the following command: + run the installer for this example using the following commands: - $ adt_installer + $ cd ~/adt-installer + $ ./adt_installer @@ -214,9 +215,9 @@ Follow these steps: Go to - + and find the folder that matches your host development system - (i.e. i586 for 32-bit machines or + (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 includes the appropriate target architecture. @@ -224,7 +225,7 @@ 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: - yocto-eglibc-x86_64-i586-toolchain-1.1.tar.bz2 + poky-eglibc-x86_64-i586-toolchain-1.1.1.tar.bz2 As an alternative to steps one and two, you can build the toolchain tarball if you have a Yocto Project build tree. @@ -244,6 +245,12 @@ The tarball expands into /opt/poky/1.1.1. Once the tarball is expanded, the cross-toolchain is installed. You will notice environment setup files for the cross-toolchain in the directory. + Here is an example where the tarball exists in the user's Downloads + directory: + + # cd / + # tar -xjf /home/scottrif/Downloads/poky-eglibc-x86_64-i586-toolchain-gmae-1.1.tar.bz2 + @@ -280,7 +287,7 @@ command. Run bitbake meta-ide-support to complete the cross-toolchain installation. - If change out of your working directory after you + If you change out of your working directory after you source the environment setup script and before you run the bitbake command, the command might not work. Be sure to run the bitbake command immediately @@ -311,14 +318,14 @@ - Be sure to run the environment setup script that matches the architecture for + Be sure to source the environment setup script that matches the architecture for which you are developing. Environment setup scripts begin with the string “environment-setup” and include as part of their name the architecture. - For example, the toolchain environment setup script for a 64-bit IA-based architecture would - be the following: + For example, the command to source the toolchain environment setup script + for a 64-bit IA-based machine would be the following: - /opt/poky/1.1.1/environment-setup-x86_64-poky-linux + $ source /opt/poky/1.1.1/environment-setup-x86_64-poky-linux @@ -341,9 +348,7 @@ pre-built versions. You can find examples for both these situations in the "A - Quick Test Run" section of - - The Yocto Project Quick Start. + Quick Test Run" section of The Yocto Project Quick Start. @@ -352,12 +357,10 @@ mips, powerpc, and arm) that you can use unaltered in the QEMU emulator. These kernel images reside in the Yocto Project release - area - + area - and are ideal for experimentation within Yocto Project. For information on the image types you can build using the Yocto Project, see the - "Reference: Images" appendix in - - The Yocto Project Reference Manual. + "Reference: Images" appendix in The Yocto Project Reference Manual. @@ -373,7 +376,7 @@ If you want to use a different image type that contains the tcf-agent, you can do so one of two ways: - Modify the conf/local.conf configuration in + Modify the conf/local.conf configuration file in the Yocto Project build directory and then rebuild the image. With this method, you need to modify the EXTRA_IMAGE_FEATURES variable to have the value of "tools-debug" before rebuilding the image. @@ -429,16 +432,17 @@ To extract the root filesystem, first source the cross-development environment setup script and then use the runqemu-extract-sdk command on the - filesystem image. - For example, the following commands set up the environment and then extract + filesystem image tarball. + For example, the following commands set up the environment by sourcing + the setup script from within the build directory and then extracting the root filesystem from a previously built filesystem image tarball named - core-image-sato-sdk-qemux86-2011091411831.rootfs.tar.bz2. + core-image-sato-sdk-qemux86.tar.bz2. The example extracts the root filesystem into the $HOME/qemux86-sato directory: $ source $HOME/poky/build/tmp/environment-setup-i586-poky-linux $ runqemu-extract-sdk \ - tmp/deploy/images/core-image-sato-sdk-qemux86-2011091411831.rootfs.tar.bz2 \ + tmp/deploy/images/core-image-sato-sdk-qemux86.tar.bz2 \ $HOME/qemux86-sato In this case, you could now point to the target sysroot at -- cgit v1.2.3-54-g00ecf