sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

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: 8c1a5e9fd114fd181b15de3b117d56fbb5779e1f)

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 2013-10-24 09:51:38 -07:00 committed by Richard Purdie
parent 4e6514248b
commit 560606c3ec
1 changed files with 40 additions and 30 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

70
documentation/adt-manual/adt-prepare.xml
View File

@ -80,38 +80,48 @@
<para> <para>
The ADT Installer is contained in the ADT Installer tarball. The ADT Installer is contained in the ADT Installer tarball.
You can download the tarball from You can get the tarball using either of these methods:
<ulink url='&YOCTO_ADTINSTALLER_DL_URL;'></ulink> into any <itemizedlist>
directory. <listitem><para><emphasis>Download the Tarball:</emphasis>
Or, you can use BitBake to generate the tarball inside the existing You can download the tarball from
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>. <ulink url='&YOCTO_ADTINSTALLER_DL_URL;'></ulink> into
</para> any directory.</para></listitem>
<listitem><para><emphasis>Build the Tarball:</emphasis>
<para> You can use BitBake to generate the tarball inside an
If you use BitBake to generate the ADT Installer tarball, you must existing
<filename>source</filename> the environment setup script <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
(<ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink> </para>
or <para>If you use BitBake to generate the ADT Installer
<ulink url='&YOCTO_DOCS_REF_URL;#structure-memres-core-script'><filename>oe-init-build-env-memres</filename></ulink>) tarball, you must <filename>source</filename> the
located in the Source Directory before running the environment setup script
BitBake command that creates the tarball. (<ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink>
</para> or
<ulink url='&YOCTO_DOCS_REF_URL;#structure-memres-core-script'><filename>oe-init-build-env-memres</filename></ulink>)
<para> located in the Source Directory before running the
The following example commands download the Poky tarball, set up the BitBake command that creates the tarball.</para>
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>, <para>The following example commands establish
set up the environment while also creating the default Build Directory, the
and run the BitBake command that results in the tarball <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>,
<filename>~/yocto-project/build/tmp/deploy/sdk/adt_installer.tar.bz2</filename>: check out the current release branch, set up the
<literallayout class='monospaced'> 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 ~ $ cd ~
$ mkdir yocto-project $ git clone git://git.yoctoproject.org/poky
$ cd yocto-project $ cd poky
$ wget &YOCTO_RELEASE_DL_URL;/&YOCTO_POKY_TARBALL; $ git checkout -b &DISTRO_NAME; origin/&DISTRO_NAME;
$ tar xjf &YOCTO_POKY_TARBALL; $ source &OE_INIT_FILE;
$ source &OE_INIT_PATH;
$ bitbake adt-installer $ bitbake adt-installer
</literallayout> </literallayout></para></listitem>
</itemizedlist>
</para> </para>
</section> </section>