diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml index 77999b8b42..1733141577 100644 --- a/documentation/adt-manual/adt-prepare.xml +++ b/documentation/adt-manual/adt-prepare.xml @@ -22,6 +22,14 @@ user-space NFS, define which root filesystem profiles to download, and allows you to define the target sysroot location. + + If you need to generate the ADT tarball you can do so using the following command: + + $ bitbake adt-installer + + This command generates the file adt-installer.tar.bz2 + in the ../build/tmp/deploy/sdk directory. +
Configuring and Running the ADT Installer @@ -120,14 +128,14 @@
Using an Existing Toolchain Tarball - If you don’t want to use the ADT Installer you can install the toolchain + If you do not want to use the ADT Installer you can install the toolchain and the sysroot by hand. Follow these steps: Locate and download the architecture-specific toolchain - tarball from . + tarball from . Look in the ‘toolchain’ folder and then open up the folder that matches your - host development system (i.e. 'i586' for 32-bit machines or 'x86_64' + host development system (i.e. 'i686' for 32-bit machines or 'x86_64' for 64-bit machines). Then, select the toolchain tarball whose name includes the appropriate target architecture.