From 678f6ee437db04cc8cd3df945a7b5ab5da0b6165 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Fri, 15 Jun 2012 06:22:29 -0700 Subject: documentation/adt-manual/adt-prepare.xml: 1.1.2 variables and updates First pass at implementing the poky.ent variables. Also updated text as needed. (From yocto-docs rev: 3472d1c2e7c69e0b544a223204830c0d000033f8) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/adt-manual/adt-prepare.xml | 76 ++++++++++++++------------------ 1 file changed, 34 insertions(+), 42 deletions(-) diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml index 79c44849e9..6098fb2737 100644 --- a/documentation/adt-manual/adt-prepare.xml +++ b/documentation/adt-manual/adt-prepare.xml @@ -1,5 +1,6 @@ +"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" +[ %poky; ] > @@ -56,9 +57,9 @@ The ADT Installer is contained in the ADT Installer tarball. You can download the tarball into any directory from the - Index of Releases, specifically + Index of Releases, specifically at - . + . Or, you can use BitBake to generate the tarball inside the existing Yocto Project build tree. @@ -81,9 +82,9 @@ $ cd ~ $ mkdir yocto-project $ cd yocto-project - $ wget http://downloads.yoctoproject.org/releases/yocto/yocto-1.1.1/poky-edison-6.0.1.tar.bz2 - $ tar xjf poky-edison-6.0.1.tar.bz2 - $ source poky-edison-6.0.1/oe-init-build-env + $ wget &YOCTO_RELEASE_DL_URL;/&YOCTO_POKY_TARBALL; + $ tar xjf &YOCTO_POKY_TARBALL; + $ source &OE_INIT_PATH; $ bitbake adt-installer @@ -100,7 +101,7 @@ a top-level directory named adt-installer: $ cd ~ - $ cp ~/yocto-project/build/tmp/deploy/sdk/adt_installer.tar.bz2 $HOME + $ cp ~/poky/build/tmp/deploy/sdk/adt_installer.tar.bz2 $HOME $ tar -xjf adt_installer.tar.bz2 Unpacking it creates the directory adt-installer, @@ -165,20 +166,17 @@ After you have configured the adt_installer.conf file, - run the installer for this example using the following commands: + run the installer using the following command: - $ cd ~/adt-installer $ ./adt_installer The ADT Installer requires the libtool package to complete. - If you install the recommended packages as described in the - "Packages" - section of - - The Yocto Project Quick Start, then you will have libtool installed. + If you install the recommended packages as described in + "The Packages" + section of The Yocto Project Quick Start, then you will have libtool installed. @@ -192,7 +190,7 @@ Once the installation completes, the ADT, which includes the cross-toolchain, is installed. You will notice environment setup files for the cross-toolchain in - /opt/poky/1.1.1, + &YOCTO_ADTPATH_DIR;, and image tarballs in the adt-installer directory according to your installer configurations, and the target sysroot located according to the YOCTOADT_TARGET_SYSROOT_LOC_<arch> variable @@ -215,17 +213,17 @@ Follow these steps: Go to - + and find the folder that matches your host development system (i.e. i686 for 32-bit machines or - x86_64 for 64-bit machines). + x86-64 for 64-bit machines). Go into that folder and download the toolchain tarball 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: - poky-eglibc-x86_64-i586-toolchain-1.1.1.tar.bz2 + poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.tar.bz2 As an alternative to steps one and two, you can build the toolchain tarball if you have a Yocto Project build tree. @@ -242,15 +240,9 @@ Make sure you are in the root directory with root privileges and then expand the tarball. - The tarball expands into /opt/poky/1.1.1. + The tarball expands into &YOCTO_ADTPATH_DIR;. 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 - @@ -287,7 +279,7 @@ command. Run bitbake meta-ide-support to complete the cross-toolchain installation. - If you change out of your working directory after you + If 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,21 +303,21 @@ Before you can develop using the cross-toolchain, you need to set up the cross-development environment by sourcing the toolchain's environment setup script. If you used the ADT Installer or used an existing ADT tarball to install the ADT, - then you can find this script in the /opt/poky/1.1.1 + then you can find this script in the &YOCTO_ADTPATH_DIR; directory. If you installed the toolchain in the build tree, you can find the environment setup script for the toolchain in the Yocto Project build tree's tmp directory. - Be sure to source the environment setup script that matches the architecture for + Be sure to run 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 command to source the toolchain environment setup script - for a 64-bit IA-based machine would be the following: + For example, the toolchain environment setup script for a 64-bit IA-based architecture would + be the following: - $ source /opt/poky/1.1.1/environment-setup-x86_64-poky-linux + &YOCTO_ADTPATH_DIR;/environment-setup-x86_64-poky-linux @@ -347,8 +339,8 @@ To get the kernel and filesystem images, you either have to build them or download pre-built versions. You can find examples for both these situations in the - "A - Quick Test Run" section of The Yocto Project Quick Start. + "A Quick Test Run" section of + The Yocto Project Quick Start. @@ -357,10 +349,11 @@ 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. @@ -391,11 +384,11 @@ Set up the cross-development environment as described in the "Setting Up the Cross-Development Environment" section. - Get the tcf-agent source code, which is - stored using the Subversion SCM, using the following command: + Get the tcf-agent source code using + the following commands: - $ svn checkout svn://dev.eclipse.org/svnroot/dsdp/org.eclipse.tm.tcf/trunk/agent \ - <-r #rev_number> + $ git clone http://git.eclipse.org/gitroot/tcf/org.eclipse.tcf.agent.git + $ cd agent Modify the Makefile.inc file for the cross-compilation environment by setting the @@ -432,9 +425,8 @@ 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 tarball. - For example, the following commands set up the environment by sourcing - the setup script from within the build directory and then extracting + filesystem image. + For example, the following commands set up the environment and then extract the root filesystem from a previously built filesystem image tarball named core-image-sato-sdk-qemux86.tar.bz2. The example extracts the root filesystem into the $HOME/qemux86-sato -- cgit v1.2.3-54-g00ecf