mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-09-14 03:49:32 +02:00
Code Issues Packages Projects Releases Wiki Activity

documentation: Toolchain corrections from tarball to .sh file

Browse Source 
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>
This commit is contained in:
Scott Rifenbark
2012-09-13 14:01:58 -07:00
committed by Richard Purdie
parent 4c90692716
commit c4a923bcb0
8 changed files with 70 additions and 46 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
documentation/yocto-project-qs/yocto-project-qs.xml
View File

@@ -526,9 +526,9 @@
<section id='installing-the-toolchain'>
<title>Installing the Toolchain</title>
<para>
You can download a tarball with the pre-built toolchain, which includes the
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
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 development systems from the
<filename>i686</filename> and <filename>x86-64</filename> directories, respectively.
@@ -539,7 +539,7 @@
</para>
<literallayout class='monospaced'>
poky-eglibc-&lt;<emphasis>host_system</emphasis>&gt;-&lt;<emphasis>arch</emphasis>&gt;-toolchain-gmae-&lt;<emphasis>release</emphasis>&gt;.tar.bz2
poky-eglibc-&lt;<emphasis>host_system</emphasis>&gt;-&lt;<emphasis>arch</emphasis>&gt;-toolchain-gmae-&lt;<emphasis>release</emphasis>&gt;.sh
Where:
&lt;<emphasis>host_system</emphasis>&gt; is a string representing your development system:
@@ -552,26 +552,33 @@
</literallayout>
<para>
For example, the following toolchain tarball is for a 64-bit development
For example, the following toolchain installer is for a 64-bit development
host system and a 32-bit target architecture:
</para>
<literallayout class='monospaced'>
poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.tar.bz2
poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.sh
</literallayout>
<para>
The toolchain tarballs are self-contained and must be installed into <filename>/opt/poky</filename>.
The following commands show how you install the toolchain tarball given a 64-bit development
host system and a 32-bit target architecture.
The example assumes the toolchain tarball is located in <filename>~/toolchains/</filename>.
You must have your working directory set to root before unpacking the tarball:
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>
The following command shows how to run the installer given a toolchain tarball
for a 64-bit development host system and a 32-bit target architecture.
The example assumes the toolchain installer is located in <filename>~/Downloads/</filename>.
<note>
If you do not have write permissions for the directory into which you are installing
the toolchain, the toolchain installer notifies you and exits.
Be sure you have write permissions in the directory and run the installer again.
</note>
</para>
<para>
<literallayout class='monospaced'>
$ cd /
$ sudo tar -xvjf ~/toolchains/poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.tar.bz2
$ ~/Downloads/poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.sh
</literallayout>
</para>