diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-09-13 14:01:58 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-09-14 09:50:52 +0100 |
commit | c4a923bcb0194c05b14d40be7ad4ecd193eb7a69 (patch) | |
tree | 6bec21f8000bfb08a8405124b78cdbdc1c22b0b6 /documentation/yocto-project-qs/yocto-project-qs.xml | |
parent | 4c90692716feb5e52f7859e2013b02f6f6703062 (diff) | |
download | poky-c4a923bcb0194c05b14d40be7ad4ecd193eb7a69.tar.gz |
documentation: Toolchain corrections from tarball to .sh file
For 1.3 there is not longer a toolchain tarball. Instead, there
is a wrapper script that lets you install the tarball. This
fundamental usage model change caused several ripples throughout
the documentation set. I have changed wordings and examples
to reflect the new paradigm.
(From yocto-docs rev: afb2069daa91e04c0f78ba425a6b184cb820d888)
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.xml | 31 |
1 files changed, 19 insertions, 12 deletions
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml index 83c204b0af..b37a45f337 100644 --- a/documentation/yocto-project-qs/yocto-project-qs.xml +++ b/documentation/yocto-project-qs/yocto-project-qs.xml | |||
@@ -526,9 +526,9 @@ | |||
526 | <section id='installing-the-toolchain'> | 526 | <section id='installing-the-toolchain'> |
527 | <title>Installing the Toolchain</title> | 527 | <title>Installing the Toolchain</title> |
528 | <para> | 528 | <para> |
529 | You can download a tarball with the pre-built toolchain, which includes the | 529 | You can download a tarball installer, which includes the pre-built toolchain, the |
530 | <filename>runqemu</filename> | 530 | <filename>runqemu</filename> |
531 | script and support files, from the appropriate directory under | 531 | script, and support files from the appropriate directory under |
532 | <ulink url='&YOCTO_TOOLCHAIN_DL_URL;'></ulink>. | 532 | <ulink url='&YOCTO_TOOLCHAIN_DL_URL;'></ulink>. |
533 | Toolchains are available for 32-bit and 64-bit development systems from the | 533 | Toolchains are available for 32-bit and 64-bit development systems from the |
534 | <filename>i686</filename> and <filename>x86-64</filename> directories, respectively. | 534 | <filename>i686</filename> and <filename>x86-64</filename> directories, respectively. |
@@ -539,7 +539,7 @@ | |||
539 | </para> | 539 | </para> |
540 | 540 | ||
541 | <literallayout class='monospaced'> | 541 | <literallayout class='monospaced'> |
542 | poky-eglibc-<<emphasis>host_system</emphasis>>-<<emphasis>arch</emphasis>>-toolchain-gmae-<<emphasis>release</emphasis>>.tar.bz2 | 542 | poky-eglibc-<<emphasis>host_system</emphasis>>-<<emphasis>arch</emphasis>>-toolchain-gmae-<<emphasis>release</emphasis>>.sh |
543 | 543 | ||
544 | Where: | 544 | Where: |
545 | <<emphasis>host_system</emphasis>> is a string representing your development system: | 545 | <<emphasis>host_system</emphasis>> is a string representing your development system: |
@@ -552,26 +552,33 @@ | |||
552 | </literallayout> | 552 | </literallayout> |
553 | 553 | ||
554 | <para> | 554 | <para> |
555 | For example, the following toolchain tarball is for a 64-bit development | 555 | For example, the following toolchain installer is for a 64-bit development |
556 | host system and a 32-bit target architecture: | 556 | host system and a 32-bit target architecture: |
557 | </para> | 557 | </para> |
558 | 558 | ||
559 | <literallayout class='monospaced'> | 559 | <literallayout class='monospaced'> |
560 | poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.tar.bz2 | 560 | poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.sh |
561 | </literallayout> | 561 | </literallayout> |
562 | 562 | ||
563 | <para> | 563 | <para> |
564 | The toolchain tarballs are self-contained and must be installed into <filename>/opt/poky</filename>. | 564 | Toolchains are self-contained and by default are installed into <filename>/opt/poky</filename>. |
565 | The following commands show how you install the toolchain tarball given a 64-bit development | 565 | However, when you run the toolchain installer, you can choose an installation directory. |
566 | host system and a 32-bit target architecture. | 566 | </para> |
567 | The example assumes the toolchain tarball is located in <filename>~/toolchains/</filename>. | 567 | |
568 | You must have your working directory set to root before unpacking the tarball: | 568 | <para> |
569 | The following command shows how to run the installer given a toolchain tarball | ||
570 | for a 64-bit development host system and a 32-bit target architecture. | ||
571 | The example assumes the toolchain installer is located in <filename>~/Downloads/</filename>. | ||
572 | <note> | ||
573 | If you do not have write permissions for the directory into which you are installing | ||
574 | the toolchain, the toolchain installer notifies you and exits. | ||
575 | Be sure you have write permissions in the directory and run the installer again. | ||
576 | </note> | ||
569 | </para> | 577 | </para> |
570 | 578 | ||
571 | <para> | 579 | <para> |
572 | <literallayout class='monospaced'> | 580 | <literallayout class='monospaced'> |
573 | $ cd / | 581 | $ ~/Downloads/poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.sh |
574 | $ sudo tar -xvjf ~/toolchains/poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.tar.bz2 | ||
575 | </literallayout> | 582 | </literallayout> |
576 | </para> | 583 | </para> |
577 | 584 | ||