From 02fa765b8e96f39e00936e1e28405e4830a72e86 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Fri, 14 Mar 2014 08:07:05 -0600 Subject: adt-manual: Added a link to BitBake term and fixed some formatting. Needed a link to the term "BitBake". Also, reformatted the occurrences of "BitBake command" into "bitbake command as they are actual command references. (From yocto-docs rev: 0a6540948edfca1f9c7c0b880d78252c5da0d8cd) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/adt-manual/adt-prepare.xml | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml index 93eba6e402..866facb53a 100644 --- a/documentation/adt-manual/adt-prepare.xml +++ b/documentation/adt-manual/adt-prepare.xml @@ -87,8 +87,9 @@ into any directory. Build the Tarball: - You can use BitBake to generate the tarball inside an - existing + You can use + BitBake + to generate the tarball inside an existing Build Directory. If you use BitBake to generate the ADT Installer @@ -98,14 +99,16 @@ or oe-init-build-env-memres) located in the Source Directory before running the - BitBake command that creates the tarball. + bitbake command that creates the + tarball. The following example commands establish the Source Directory, check out the current release branch, set up the build environment while also creating the default - Build Directory, and run the BitBake command that - results in the tarball + Build Directory, and run the + bitbake command that results in the + tarball poky/build/tmp/deploy/sdk/adt_installer.tar.bz2: Before using BitBake to build the ADT tarball, be -- cgit v1.2.3-54-g00ecf