diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 3d0cfd42fb..8776645207 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -622,50 +622,56 @@
As an alternative to locating and downloading a toolchain installer,
- you can build the toolchain installer one of two ways if you have a
- Build Directory:
-
-
- Use bitbake meta-toolchain.
- This method requires you to still install the target
- sysroot by installing and extracting it separately.
- For information on how to install the sysroot, see the
- "Extracting the Root Filesystem"
- section.
-
-
- Use bitbakeimage-c populate_sdk.
- This method has significant advantages over the previous method
- because it results in a toolchain installer that contains the
- sysroot that matches your target root filesystem.
-
+ you can build the toolchain installer if you have a
+ Build Directory.
+
+ Although not the preferred method, it is also possible to use
+ bitbake meta-toolchain to build the toolchain
+ installer.
+ If you do use this method, you must separately install and extract
+ the target sysroot.
+ For information on how to install the sysroot, see the
+ "Extracting the Root Filesystem"
+ section.
+
+
- Another powerful feature is that the toolchain is
- completely self-contained.
- The binaries are linked against their own copy of
- libc, which results in no dependencies
- on the target system.
- To achieve this, the pointer to the dynamic loader is
- configured at install time since that path cannot be dynamically
- altered.
- This is the reason for a wrapper around the
- populate_sdk archive.
+
+ To build the toolchain installer and populate the SDK image, use the
+ following command:
+
+ $ bitbake image -c populate_sdk
+
+ The command results in a toolchain installer that contains the sysroot
+ that matches your target root filesystem.
+
- Another feature is that only one set of cross-canadian
- toolchain binaries are produced per architecture.
- This feature takes advantage of the fact that the target
- hardware can be passed to gcc as a set of
- compiler options.
- Those options are set up by the environment script and
- contained in variables such as
- CC
- and
- LD.
- This reduces the space needed for the tools.
- Understand, however, that a sysroot is still needed for every
- target since those binaries are target-specific.
-
-
+
+ Another powerful feature is that the toolchain is completely
+ self-contained.
+ The binaries are linked against their own copy of
+ libc, which results in no dependencies
+ on the target system.
+ To achieve this, the pointer to the dynamic loader is
+ configured at install time since that path cannot be dynamically
+ altered.
+ This is the reason for a wrapper around the
+ populate_sdk archive.
+
+
+
+ Another feature is that only one set of cross-canadian toolchain
+ binaries are produced per architecture.
+ This feature takes advantage of the fact that the target hardware can
+ be passed to gcc as a set of compiler options.
+ Those options are set up by the environment script and contained in
+ variables such as
+ CC
+ and
+ LD.
+ This reduces the space needed for the tools.
+ Understand, however, that a sysroot is still needed for every target
+ since those binaries are target-specific.