diff options
| author |   Scott Rifenbark <scott.m.rifenbark@intel.com> | 2013-08-26 11:17:49 +0300 |
|---|---|---|
| committer |   Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-08-26 11:06:30 +0100 |
| commit | e901047d4db48fc5e5f20d71fa20601a9e735ab6 (patch) | |
| tree | 5fabaf4420963e6f43b12dd888179be7e7f8f396 /documentation/yocto-project-qs | |
| parent | 648da6d502e7253873dd9759a2482895d7f0159b (diff) | |
| download | openembedded-core-contrib-e901047d4db48fc5e5f20d71fa20601a9e735ab6.tar.gz | |
yocto-project-qs, adt-manual: Updates to toolchain installer script
The way in which the toolchain installer scripts are named has
changed. I have updated two sections that describe this so that
the new naming scheme is used.
(From yocto-docs rev: 71b70a12c72bca7cad565b5d6f44b2c6b311844d)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/yocto-project-qs')
| -rw-r--r-- | documentation/yocto-project-qs/yocto-project-qs.xml | 60 |
1 files changed, 39 insertions, 21 deletions
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml index a8e8c3a35a..372a86efd0 100644 --- a/documentation/yocto-project-qs/yocto-project-qs.xml +++ b/documentation/yocto-project-qs/yocto-project-qs.xml @@ -552,44 +552,62 @@ <section id='installing-the-toolchain'> <title>Installing the Toolchain</title> + <para> - You can download a tarball installer, which includes the pre-built toolchain, the - <filename>runqemu</filename> + You can download a tarball installer, which includes the + pre-built toolchain, the <filename>runqemu</filename> script, and support files from the appropriate directory under <ulink url='&YOCTO_TOOLCHAIN_DL_URL;'></ulink>. - Toolchains are available for 32-bit and 64-bit x86 development systems from the - <filename>i686</filename> and <filename>x86_64</filename> directories, respectively. - Each type of development system supports five target architectures. - The names of the tarball installer scripts are such that a string representing the - host system appears first in the filename and then is immediately followed by a - string representing the target architecture. + Toolchains are available for 32-bit and 64-bit x86 development + systems from the <filename>i686</filename> and + <filename>x86_64</filename> directories, respectively. + The toolchains the Yocto Project provides are based off the + <filename>core-image-sato</filename> image and contain + libraries appropriate for developing against that image. + Each type of development system supports five or more target + architectures. + </para> + + <para> + The names of the tarball installer scripts are such that a + string representing the host system appears first in the + filename and then is immediately followed by a string + that represents the target architecture. </para> <literallayout class='monospaced'> - poky-eglibc-<<emphasis>host_system</emphasis>>-<<emphasis>arch</emphasis>>-toolchain-gmae-<<emphasis>release</emphasis>>.sh + poky-eglibc-<<emphasis>host_system</emphasis>>-<<emphasis>image_type</emphasis>>-<<emphasis>arch</emphasis>>.sh Where: <<emphasis>host_system</emphasis>> is a string representing your development system: i686 or x86_64. - <<emphasis>arch</emphasis>> is a string representing the target architecture: - i586, x86_64, powerpc, mips, or arm. + <<emphasis>image_type</emphasis>> is a string representing the image you wish to + develop a Software Development Toolkit (SDK) for use against. + The Yocto Project builds toolchain installers using the + following BitBake command: + + bitbake core-image-sato -c do_populatesdk core-image-sato - <<emphasis>release</emphasis>> is the version of Yocto Project. + <<emphasis>arch</emphasis>> is a string representing the tuned target architecture: + + i586, x86_64, powerpc, mips, armv7a or armv5te </literallayout> <para> - For example, the following toolchain installer is for a 64-bit development - host system and a 32-bit target architecture: + For example, the following toolchain installer is for a 64-bit + development host system and a i586-tuned target architecture + based off the SDK for <filename>core-image-sato</filename>: + <literallayout class='monospaced'> + poky-eglibc-x86_64-core-image-sato-i586.sh + </literallayout> </para> - <literallayout class='monospaced'> - poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.sh - </literallayout> - <para> - Toolchains are self-contained and by default are installed into <filename>/opt/poky</filename>. - However, when you run the toolchain installer, you can choose an installation directory. + Toolchains are self-contained and by default are installed into + <filename>/opt/poky</filename>. + However, when you run the toolchain installer, you can choose an + installation directory. </para> <para> @@ -610,7 +628,7 @@ <para> <literallayout class='monospaced'> - $ ~/Downloads/poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.sh + $ ~/Downloads/poky-eglibc-x86_64-core-image-sato-i586.sh </literallayout> </para> |