diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml index b4e27baf6f..152c7fbfa6 100644 --- a/documentation/adt-manual/adt-prepare.xml +++ b/documentation/adt-manual/adt-prepare.xml @@ -582,30 +582,26 @@ As an alternative to locating and downloading a toolchain installer, - you can build the toolchain installer if you have a - Build Directory. + 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 + bitbake image -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 using 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. - - - - A final method of building the toolchain installer exists that has - significant advantages over the previous method. - This method results in a toolchain installer that contains the sysroot - that matches your target root filesystem. - To build this installer, use the - bitbake image -c populate_sdk command. - - - - Remember, before using any bitbake command, you + Remember, before using any BitBake command, you must source the build environment setup script (i.e. &OE_INIT_FILE;