diff options
| author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2013-10-24 09:51:38 -0700 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-11-01 17:09:52 +0000 |
| commit | 122e688d596c0b1b936bdd526bd30f238aaa9a71 (patch) | |
| tree | d16acc2069c512a470c2ce01ffed44a56d8e5d5c | |
| parent | 610ccdb75fe9be61190df129bbc5c741ba333c31 (diff) | |
| download | 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>
| -rw-r--r-- | documentation/adt-manual/adt-prepare.xml | 70 |
1 files changed, 40 insertions, 30 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml index 9c016bf32c..e0973c4e11 100644 --- a/documentation/adt-manual/adt-prepare.xml +++ b/documentation/adt-manual/adt-prepare.xml | |||
| @@ -80,38 +80,48 @@ | |||
| 80 | 80 | ||
| 81 | <para> | 81 | <para> |
| 82 | The ADT Installer is contained in the ADT Installer tarball. | 82 | The ADT Installer is contained in the ADT Installer tarball. |
| 83 | You can download the tarball from | 83 | You can get the tarball using either of these methods: |
| 84 | <ulink url='&YOCTO_ADTINSTALLER_DL_URL;'></ulink> into any | 84 | <itemizedlist> |
| 85 | directory. | 85 | <listitem><para><emphasis>Download the Tarball:</emphasis> |
| 86 | Or, you can use BitBake to generate the tarball inside the existing | 86 | You can download the tarball from |
| 87 | <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>. | 87 | <ulink url='&YOCTO_ADTINSTALLER_DL_URL;'></ulink> into |
| 88 | </para> | 88 | any directory.</para></listitem> |
| 89 | 89 | <listitem><para><emphasis>Build the Tarball:</emphasis> | |
| 90 | <para> | 90 | You can use BitBake to generate the tarball inside an |
| 91 | If you use BitBake to generate the ADT Installer tarball, you must | 91 | existing |
| 92 | <filename>source</filename> the environment setup script | 92 | <ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>. |
| 93 | (<ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink> | 93 | </para> |
| 94 | or | 94 | <para>If you use BitBake to generate the ADT Installer |
| 95 | <ulink url='&YOCTO_DOCS_REF_URL;#structure-memres-core-script'><filename>oe-init-build-env-memres</filename></ulink>) | 95 | tarball, you must <filename>source</filename> the |
| 96 | located in the Source Directory before running the | 96 | environment setup script |
| 97 | BitBake command that creates the tarball. | 97 | (<ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink> |
| 98 | </para> | 98 | or |
| 99 | 99 | <ulink url='&YOCTO_DOCS_REF_URL;#structure-memres-core-script'><filename>oe-init-build-env-memres</filename></ulink>) | |
| 100 | <para> | 100 | located in the Source Directory before running the |
| 101 | The following example commands download the Poky tarball, set up the | 101 | BitBake command that creates the tarball.</para> |
| 102 | <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>, | 102 | <para>The following example commands establish |
| 103 | set up the environment while also creating the default Build Directory, | 103 | the |
| 104 | and run the BitBake command that results in the tarball | 104 | <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>, |
| 105 | <filename>~/yocto-project/build/tmp/deploy/sdk/adt_installer.tar.bz2</filename>: | 105 | check out the current release branch, set up the |
| 106 | <literallayout class='monospaced'> | 106 | build environment while also creating the default |
| 107 | Build Directory, and run the BitBake command that | ||
| 108 | results in the tarball | ||
| 109 | <filename>~/yocto-project/build/tmp/deploy/sdk/adt_installer.tar.bz2</filename>: | ||
| 110 | <note> | ||
| 111 | Before using BitBake to build the ADT tarball, be | ||
| 112 | sure to make sure your | ||
| 113 | <filename>local.conf</filename> file is properly | ||
| 114 | configured. | ||
| 115 | </note> | ||
| 116 | <literallayout class='monospaced'> | ||
| 107 | $ cd ~ | 117 | $ cd ~ |
| 108 | $ mkdir yocto-project | 118 | $ git clone git://git.yoctoproject.org/poky |
| 109 | $ cd yocto-project | 119 | $ cd poky |
| 110 | $ wget &YOCTO_RELEASE_DL_URL;/&YOCTO_POKY_TARBALL; | 120 | $ git checkout -b &DISTRO_NAME; origin/&DISTRO_NAME; |
| 111 | $ tar xjf &YOCTO_POKY_TARBALL; | 121 | $ source &OE_INIT_FILE; |
| 112 | $ source &OE_INIT_PATH; | ||
| 113 | $ bitbake adt-installer | 122 | $ bitbake adt-installer |
| 114 | </literallayout> | 123 | </literallayout></para></listitem> |
| 124 | </itemizedlist> | ||
| 115 | </para> | 125 | </para> |
| 116 | </section> | 126 | </section> |
| 117 | 127 | ||
