From a4266b454cad4cab43de4c6fc823ff2c4e53e5c9 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Mon, 22 Oct 2012 10:28:05 -0700 Subject: documentation: adt-manual - final edits before 1.3 lockdown. Made some minor edits to the book before locking down the files for 1.3. (From yocto-docs rev: 2b941103585a31b5dbcb65b784cc3381467ed697) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/adt-manual/adt-prepare.xml | 38 ++++++++++++++++---------------- 1 file changed, 19 insertions(+), 19 deletions(-) (limited to 'documentation/adt-manual/adt-prepare.xml') diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml index d660480b73..2e57e0cbe5 100644 --- a/documentation/adt-manual/adt-prepare.xml +++ b/documentation/adt-manual/adt-prepare.xml @@ -52,7 +52,7 @@ get any of the other mentioned benefits had you run the ADT Installer script. Use the Toolchain from within the Build Directory: If you already have a - build directory, + Build Directory, you can build the cross-toolchain within the directory. However, like the previous method mentioned, you only get the cross-toolchain and QEMU - you do not get any of the other benefits without taking separate steps. @@ -77,21 +77,21 @@ at . Or, you can use BitBake to generate the tarball inside the existing - build directory. + Build Directory. If you use BitBake to generate the ADT Installer tarball, you must source the environment setup script (&OE_INIT_FILE;) located - in the source directory before running the bitbake + in the Source Directory before running the bitbake command that creates the tarball. The following example commands download the Poky tarball, set up the - source directory, - set up the environment while also creating the default build directory, + Source Directory, + set up the environment while also creating the default Build Directory, and run the bitbake command that results in the tarball ~/yocto-project/build/tmp/deploy/sdk/adt_installer.tar.bz2: @@ -251,7 +251,7 @@ poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.sh As an alternative to steps one and two, you can build the toolchain installer - if you have a build directory. + if you have a Build Directory. If you need GMAE, you should use the bitbake meta-toolchain-gmae command. The resulting installation script when run will support such development. @@ -259,10 +259,10 @@ 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. + sourced the &OE_INIT_PATH; script located in the Source + Directory. When the bitbake command completes, the toolchain installer will - be in tmp/deploy/sdk in the build directory. + be in tmp/deploy/sdk in the Build Directory. Once you have the installer, run it to install the toolchain. @@ -292,7 +292,7 @@ A final way of making the cross-toolchain available is to use BitBake to generate the toolchain within an existing - build directory. + Build Directory. This method does not install the toolchain into the /opt directory. As with the previous method, if you need to install the target sysroot, you must @@ -300,20 +300,20 @@ - Follow these steps to generate the toolchain into the build directory: + Follow these steps to generate the toolchain into the Build Directory: Source the environment setup script &OE_INIT_FILE; located in the - source directory. + Source Directory. At this point, you should be sure that the MACHINE variable in the local.conf file found in the - conf directory of the build directory + conf directory of the Build Directory is set for the target architecture. Comments within the local.conf file list the values you can use for the MACHINE variable. - You can populate the build directory with the cross-toolchains for more + You can populate the Build Directory with the cross-toolchains for more than a single architecture. You just need to edit the MACHINE variable in the local.conf file and re-run the BitBake @@ -327,9 +327,9 @@ after checking or editing the local.conf but without changing out of your working directory. Once the bitbake command finishes, - the cross-toolchain is generated and populated within the build directory. + the cross-toolchain is generated and populated within the Build Directory. You will notice environment setup files for the cross-toolchain in the - build directory in the tmp directory. + Build Directory in the tmp directory. Setup script filenames contain the strings environment-setup. Be aware that when you use this method to install the toolchain you still need to separately extract and install the sysroot filesystem. @@ -351,9 +351,9 @@ then you can find this script in the &YOCTO_ADTPATH_DIR; directory. If you installed the toolchain in the - build directory, + Build Directory, you can find the environment setup - script for the toolchain in the build directory's tmp directory. + script for the toolchain in the Build Directory's tmp directory. @@ -426,7 +426,7 @@ you can do so one of two ways: Modify the conf/local.conf configuration in - the build directory + the Build Directory and then rebuild the image. With this method, you need to modify the EXTRA_IMAGE_FEATURES -- cgit v1.2.3-54-g00ecf