summaryrefslogtreecommitdiffstats
path: root/documentation
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2014-03-14 08:07:05 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-03-25 12:29:39 +0000
commit02fa765b8e96f39e00936e1e28405e4830a72e86 (patch)
tree200aca89b39f097de37cc0807b18b54b96959d77 /documentation
parent720cdabe9b95489c325af1b006e9c19c266b196b (diff)
downloadpoky-02fa765b8e96f39e00936e1e28405e4830a72e86.tar.gz
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>
Diffstat (limited to 'documentation')
-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 93eba6e402..866facb53a 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -87,8 +87,9 @@
87 <ulink url='&YOCTO_ADTINSTALLER_DL_URL;'></ulink> into 87 <ulink url='&YOCTO_ADTINSTALLER_DL_URL;'></ulink> into
88 any directory.</para></listitem> 88 any directory.</para></listitem>
89 <listitem><para><emphasis>Build the Tarball:</emphasis> 89 <listitem><para><emphasis>Build the Tarball:</emphasis>
90 You can use BitBake to generate the tarball inside an 90 You can use
91 existing 91 <ulink url='&YOCTO_DOCS_DEV_URL;#bitbake-term'>BitBake</ulink>
92 to generate the tarball inside an existing
92 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>. 93 <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
93 </para> 94 </para>
94 <para>If you use BitBake to generate the ADT Installer 95 <para>If you use BitBake to generate the ADT Installer
@@ -98,14 +99,16 @@
98 or 99 or
99 <ulink url='&YOCTO_DOCS_REF_URL;#structure-memres-core-script'><filename>oe-init-build-env-memres</filename></ulink>) 100 <ulink url='&YOCTO_DOCS_REF_URL;#structure-memres-core-script'><filename>oe-init-build-env-memres</filename></ulink>)
100 located in the Source Directory before running the 101 located in the Source Directory before running the
101 BitBake command that creates the tarball.</para> 102 <filename>bitbake</filename> command that creates the
103 tarball.</para>
102 <para>The following example commands establish 104 <para>The following example commands establish
103 the 105 the
104 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>, 106 <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>,
105 check out the current release branch, set up the 107 check out the current release branch, set up the
106 build environment while also creating the default 108 build environment while also creating the default
107 Build Directory, and run the BitBake command that 109 Build Directory, and run the
108 results in the tarball 110 <filename>bitbake</filename> command that results in the
111 tarball
109 <filename>poky/build/tmp/deploy/sdk/adt_installer.tar.bz2</filename>: 112 <filename>poky/build/tmp/deploy/sdk/adt_installer.tar.bz2</filename>:
110 <note> 113 <note>
111 Before using BitBake to build the ADT tarball, be 114 Before using BitBake to build the ADT tarball, be