summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/adt-manual/adt-prepare.xml13
1 files changed, 8 insertions, 5 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 93eba6e..866facb 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -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
OpenPOWER on IntegriCloud