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 "<filename>bitbake</filename>
command as they are actual command references.

(From yocto-docs rev: 0a6540948edfca1f9c7c0b880d78252c5da0d8cd)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2014-03-14 08:07:05 -06:00 committed by Richard Purdie
parent 720cdabe9b
commit 02fa765b8e
1 changed files with 8 additions and 5 deletions

View File

@ -87,8 +87,9 @@
<ulink url='&YOCTO_ADTINSTALLER_DL_URL;'></ulink> into
any directory.</para></listitem>
<listitem><para><emphasis>Build the Tarball:</emphasis>
You can use BitBake to generate the tarball inside an
existing
You can use
<ulink url='&YOCTO_DOCS_DEV_URL;#bitbake-term'>BitBake</ulink>
to generate the tarball inside an existing
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
</para>
<para>If you use BitBake to generate the ADT Installer
@ -98,14 +99,16 @@
or
<ulink url='&YOCTO_DOCS_REF_URL;#structure-memres-core-script'><filename>oe-init-build-env-memres</filename></ulink>)
located in the Source Directory before running the
BitBake command that creates the tarball.</para>
<filename>bitbake</filename> command that creates the
tarball.</para>
<para>The following example commands establish
the
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>,
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
<filename>bitbake</filename> command that results in the
tarball
<filename>poky/build/tmp/deploy/sdk/adt_installer.tar.bz2</filename>:
<note>
Before using BitBake to build the ADT tarball, be