summaryrefslogtreecommitdiffstats
path: root/documentation/adt-manual
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-10-24 09:51:38 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-11-01 17:09:52 +0000
commit122e688d596c0b1b936bdd526bd30f238aaa9a71 (patch)
treed16acc2069c512a470c2ce01ffed44a56d8e5d5c /documentation/adt-manual
parent610ccdb75fe9be61190df129bbc5c741ba333c31 (diff)
downloadast2050-yocto-poky-122e688d596c0b1b936bdd526bd30f238aaa9a71.zip
ast2050-yocto-poky-122e688d596c0b1b936bdd526bd30f238aaa9a71.tar.gz
adt-manual: Removed tarball method from "Getting the ADT Installer Tarball"
Fixes [YOCTO #5368] Partial fix to this issue. This section demonstrated how to build the ADT Installer tarball using BitBake by downloading the poky release tarball. I updated the section to use the method where you use Git to clone the poky repo and then check out the current release as a branch. I also re-organized the section to read better. (From yocto-docs rev: 116779a3fa776a4eeb283b238bc2b5fb7202ffb4) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/adt-manual')
-rw-r--r--documentation/adt-manual/adt-prepare.xml70
1 files changed, 40 insertions, 30 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 9c016bf..e0973c4 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -80,38 +80,48 @@
<para>
The ADT Installer is contained in the ADT Installer tarball.
- You can download the tarball from
- <ulink url='&YOCTO_ADTINSTALLER_DL_URL;'></ulink> into any
- directory.
- Or, you can use BitBake to generate the tarball inside the existing
- <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
- </para>
-
- <para>
- If you use BitBake to generate the ADT Installer tarball, you must
- <filename>source</filename> the environment setup script
- (<ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink>
- 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>
-
- <para>
- The following example commands download the Poky tarball, set up the
- <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>,
- set up the environment while also creating the default Build Directory,
- and run the BitBake command that results in the tarball
- <filename>~/yocto-project/build/tmp/deploy/sdk/adt_installer.tar.bz2</filename>:
- <literallayout class='monospaced'>
+ You can get the tarball using either of these methods:
+ <itemizedlist>
+ <listitem><para><emphasis>Download the Tarball:</emphasis>
+ You can download the tarball from
+ <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
+ <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
+ </para>
+ <para>If you use BitBake to generate the ADT Installer
+ tarball, you must <filename>source</filename> the
+ environment setup script
+ (<ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink>
+ 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>
+ <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
+ <filename>~/yocto-project/build/tmp/deploy/sdk/adt_installer.tar.bz2</filename>:
+ <note>
+ Before using BitBake to build the ADT tarball, be
+ sure to make sure your
+ <filename>local.conf</filename> file is properly
+ configured.
+ </note>
+ <literallayout class='monospaced'>
$ cd ~
- $ mkdir yocto-project
- $ cd yocto-project
- $ wget &YOCTO_RELEASE_DL_URL;/&YOCTO_POKY_TARBALL;
- $ tar xjf &YOCTO_POKY_TARBALL;
- $ source &OE_INIT_PATH;
+ $ git clone git://git.yoctoproject.org/poky
+ $ cd poky
+ $ git checkout -b &DISTRO_NAME; origin/&DISTRO_NAME;
+ $ source &OE_INIT_FILE;
$ bitbake adt-installer
- </literallayout>
+ </literallayout></para></listitem>
+ </itemizedlist>
</para>
</section>
OpenPOWER on IntegriCloud