diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2013-09-16 13:52:30 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-09-22 12:20:47 +0100 |
commit | f5686c9f42856878b2957d1f5a7bc39b52eb5af2 (patch) | |
tree | 78c843485d6864c9c0469c1ede9f6b06d938e252 | |
parent | 110e8039c7fbebcd6c459c4d6b8b0e81964bf040 (diff) | |
download | poky-f5686c9f42856878b2957d1f5a7bc39b52eb5af2.tar.gz |
adt-manual: Updated location for toolball install scripts.
This now has the release_number as part of the name.
(From yocto-docs rev: e91b2a553e6f1e5ca007535d926af6df449ed20c)
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 | 19 |
1 files changed, 10 insertions, 9 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml index 38963cc099..3c50cf90e9 100644 --- a/documentation/adt-manual/adt-prepare.xml +++ b/documentation/adt-manual/adt-prepare.xml | |||
@@ -92,7 +92,7 @@ | |||
92 | If you use BitBake to generate the ADT Installer tarball, you must | 92 | If you use BitBake to generate the ADT Installer tarball, you must |
93 | <filename>source</filename> the environment setup script | 93 | <filename>source</filename> the environment setup script |
94 | (<ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink> | 94 | (<ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink> |
95 | or | 95 | or |
96 | <ulink url='&YOCTO_DOCS_REF_URL;#structure-memres-core-script'><filename>oe-init-build-env-memres</filename></ulink>) | 96 | <ulink url='&YOCTO_DOCS_REF_URL;#structure-memres-core-script'><filename>oe-init-build-env-memres</filename></ulink>) |
97 | located in the Source Directory before running the | 97 | located in the Source Directory before running the |
98 | BitBake command that creates the tarball. | 98 | BitBake command that creates the tarball. |
@@ -268,7 +268,7 @@ | |||
268 | target, go into the <filename>x86_64</filename> | 268 | target, go into the <filename>x86_64</filename> |
269 | folder and download the following installer: | 269 | folder and download the following installer: |
270 | <literallayout class='monospaced'> | 270 | <literallayout class='monospaced'> |
271 | poky-eglibc-x86_64-core-image-sato-i586.sh | 271 | poky-eglibc-x86_64-core-image-sato-i586-&DISTRO;.sh |
272 | </literallayout></para></listitem> | 272 | </literallayout></para></listitem> |
273 | <listitem><para>Build your own toolchain installer. | 273 | <listitem><para>Build your own toolchain installer. |
274 | For cases where you cannot use an installer | 274 | For cases where you cannot use an installer |
@@ -287,7 +287,7 @@ | |||
287 | The example assumes the toolchain installer is located | 287 | The example assumes the toolchain installer is located |
288 | in <filename>~/Downloads/</filename>. | 288 | in <filename>~/Downloads/</filename>. |
289 | <literallayout class='monospaced'> | 289 | <literallayout class='monospaced'> |
290 | $ ~/Downloads/poky-eglibc-x86_64-core-image-sato-i586.sh | 290 | $ ~/Downloads/poky-eglibc-x86_64-core-image-sato-i586-&DISTRO;.sh |
291 | </literallayout> | 291 | </literallayout> |
292 | <note> | 292 | <note> |
293 | If you do not have write permissions for the directory | 293 | If you do not have write permissions for the directory |
@@ -376,10 +376,11 @@ | |||
376 | </para> | 376 | </para> |
377 | 377 | ||
378 | <para> | 378 | <para> |
379 | Be sure to run the environment setup script that matches the architecture for | 379 | Be sure to run the environment setup script that matches the |
380 | which you are developing. | 380 | architecture for which you are developing. |
381 | Environment setup scripts begin with the string "<filename>environment-setup</filename>" | 381 | Environment setup scripts begin with the string |
382 | and include as part of their name the architecture. | 382 | "<filename>environment-setup</filename>" and include as part of their |
383 | name the architecture. | ||
383 | For example, the toolchain environment setup script for a 64-bit | 384 | For example, the toolchain environment setup script for a 64-bit |
384 | IA-based architecture installed in the default installation directory | 385 | IA-based architecture installed in the default installation directory |
385 | would be the following: | 386 | would be the following: |
@@ -542,7 +543,7 @@ | |||
542 | 543 | ||
543 | <para> | 544 | <para> |
544 | A final method of building the toolchain installer exists that has | 545 | A final method of building the toolchain installer exists that has |
545 | significant advantages over the previous two methods. | 546 | significant advantages over the previous method. |
546 | This method results in a toolchain installer that contains the sysroot | 547 | This method results in a toolchain installer that contains the sysroot |
547 | that matches your target root filesystem. | 548 | that matches your target root filesystem. |
548 | To build this installer, use the | 549 | To build this installer, use the |
@@ -551,7 +552,7 @@ | |||
551 | 552 | ||
552 | <para> | 553 | <para> |
553 | Remember, before using any <filename>bitbake</filename> command, you | 554 | Remember, before using any <filename>bitbake</filename> command, you |
554 | must source the build environment setup script | 555 | must source the build environment setup script |
555 | (i.e. | 556 | (i.e. |
556 | <ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink> | 557 | <ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink> |
557 | or | 558 | or |