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 /documentation | |
| parent | 110e8039c7fbebcd6c459c4d6b8b0e81964bf040 (diff) | |
| download | openembedded-core-contrib-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>
Diffstat (limited to 'documentation')
| -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 @@ 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 + 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. @@ -268,7 +268,7 @@ target, go into the <filename>x86_64</filename> folder and download the following installer: <literallayout class='monospaced'> - poky-eglibc-x86_64-core-image-sato-i586.sh + poky-eglibc-x86_64-core-image-sato-i586-&DISTRO;.sh </literallayout></para></listitem> <listitem><para>Build your own toolchain installer. For cases where you cannot use an installer @@ -287,7 +287,7 @@ The example assumes the toolchain installer is located in <filename>~/Downloads/</filename>. <literallayout class='monospaced'> - $ ~/Downloads/poky-eglibc-x86_64-core-image-sato-i586.sh + $ ~/Downloads/poky-eglibc-x86_64-core-image-sato-i586-&DISTRO;.sh </literallayout> <note> If you do not have write permissions for the directory @@ -376,10 +376,11 @@ </para> <para> - Be sure to run the environment setup script that matches the architecture for - which you are developing. - Environment setup scripts begin with the string "<filename>environment-setup</filename>" - and include as part of their name the architecture. + Be sure to run the environment setup script that matches the + architecture for which you are developing. + Environment setup scripts begin with the string + "<filename>environment-setup</filename>" and include as part of their + name the architecture. For example, the toolchain environment setup script for a 64-bit IA-based architecture installed in the default installation directory would be the following: @@ -542,7 +543,7 @@ <para> A final method of building the toolchain installer exists that has - significant advantages over the previous two methods. + significant advantages over the previous method. This method results in a toolchain installer that contains the sysroot that matches your target root filesystem. To build this installer, use the @@ -551,7 +552,7 @@ <para> Remember, before using any <filename>bitbake</filename> command, you - must source the build environment setup script + must source the build environment setup script (i.e. <ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink> or |