summaryrefslogtreecommitdiffstats
path: root/documentation/yocto-project-qs/yocto-project-qs.xml
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-08-26 11:17:49 +0300
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-08-26 11:06:30 +0100
commite901047d4db48fc5e5f20d71fa20601a9e735ab6 (patch)
tree5fabaf4420963e6f43b12dd888179be7e7f8f396 /documentation/yocto-project-qs/yocto-project-qs.xml
parent648da6d502e7253873dd9759a2482895d7f0159b (diff)
downloadpoky-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/yocto-project-qs.xml')
-rw-r--r--documentation/yocto-project-qs/yocto-project-qs.xml60
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 @@
552 552
553 <section id='installing-the-toolchain'> 553 <section id='installing-the-toolchain'>
554 <title>Installing the Toolchain</title> 554 <title>Installing the Toolchain</title>
555
555 <para> 556 <para>
556 You can download a tarball installer, which includes the pre-built toolchain, the 557 You can download a tarball installer, which includes the
557 <filename>runqemu</filename> 558 pre-built toolchain, the <filename>runqemu</filename>
558 script, and support files from the appropriate directory under 559 script, and support files from the appropriate directory under
559 <ulink url='&YOCTO_TOOLCHAIN_DL_URL;'></ulink>. 560 <ulink url='&YOCTO_TOOLCHAIN_DL_URL;'></ulink>.
560 Toolchains are available for 32-bit and 64-bit x86 development systems from the 561 Toolchains are available for 32-bit and 64-bit x86 development
561 <filename>i686</filename> and <filename>x86_64</filename> directories, respectively. 562 systems from the <filename>i686</filename> and
562 Each type of development system supports five target architectures. 563 <filename>x86_64</filename> directories, respectively.
563 The names of the tarball installer scripts are such that a string representing the 564 The toolchains the Yocto Project provides are based off the
564 host system appears first in the filename and then is immediately followed by a 565 <filename>core-image-sato</filename> image and contain
565 string representing the target architecture. 566 libraries appropriate for developing against that image.
567 Each type of development system supports five or more target
568 architectures.
569 </para>
570
571 <para>
572 The names of the tarball installer scripts are such that a
573 string representing the host system appears first in the
574 filename and then is immediately followed by a string
575 that represents the target architecture.
566 </para> 576 </para>
567 577
568 <literallayout class='monospaced'> 578 <literallayout class='monospaced'>
569 poky-eglibc-&lt;<emphasis>host_system</emphasis>&gt;-&lt;<emphasis>arch</emphasis>&gt;-toolchain-gmae-&lt;<emphasis>release</emphasis>&gt;.sh 579 poky-eglibc-&lt;<emphasis>host_system</emphasis>&gt;-&lt;<emphasis>image_type</emphasis>&gt;-&lt;<emphasis>arch</emphasis>&gt;.sh
570 580
571 Where: 581 Where:
572 &lt;<emphasis>host_system</emphasis>&gt; is a string representing your development system: 582 &lt;<emphasis>host_system</emphasis>&gt; is a string representing your development system:
573 i686 or x86_64. 583 i686 or x86_64.
574 584
575 &lt;<emphasis>arch</emphasis>&gt; is a string representing the target architecture: 585 &lt;<emphasis>image_type</emphasis>&gt; is a string representing the image you wish to
576 i586, x86_64, powerpc, mips, or arm. 586 develop a Software Development Toolkit (SDK) for use against.
587 The Yocto Project builds toolchain installers using the
588 following BitBake command:
589
590 bitbake core-image-sato -c do_populatesdk core-image-sato
577 591
578 &lt;<emphasis>release</emphasis>&gt; is the version of Yocto Project. 592 &lt;<emphasis>arch</emphasis>&gt; is a string representing the tuned target architecture:
593
594 i586, x86_64, powerpc, mips, armv7a or armv5te
579 </literallayout> 595 </literallayout>
580 596
581 <para> 597 <para>
582 For example, the following toolchain installer is for a 64-bit development 598 For example, the following toolchain installer is for a 64-bit
583 host system and a 32-bit target architecture: 599 development host system and a i586-tuned target architecture
600 based off the SDK for <filename>core-image-sato</filename>:
601 <literallayout class='monospaced'>
602 poky-eglibc-x86_64-core-image-sato-i586.sh
603 </literallayout>
584 </para> 604 </para>
585 605
586 <literallayout class='monospaced'>
587 poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.sh
588 </literallayout>
589
590 <para> 606 <para>
591 Toolchains are self-contained and by default are installed into <filename>/opt/poky</filename>. 607 Toolchains are self-contained and by default are installed into
592 However, when you run the toolchain installer, you can choose an installation directory. 608 <filename>/opt/poky</filename>.
609 However, when you run the toolchain installer, you can choose an
610 installation directory.
593 </para> 611 </para>
594 612
595 <para> 613 <para>
@@ -610,7 +628,7 @@
610 628
611 <para> 629 <para>
612 <literallayout class='monospaced'> 630 <literallayout class='monospaced'>
613 $ ~/Downloads/poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.sh 631 $ ~/Downloads/poky-eglibc-x86_64-core-image-sato-i586.sh
614 </literallayout> 632 </literallayout>
615 </para> 633 </para>
616 634