sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

adt-manual: Organized building a toolchain installer into a section. 

An improvement to expose the method by which the user gets a
toolchain installer.  I placed this information in a section of
its own rather than having it buried in a note.

(From yocto-docs rev: a1c2bb48f47cee9ee8c5c079afbcf77a793ca791)

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 2013-08-09 10:40:32 +03:00 committed by Richard Purdie
parent 089fcba0c5
commit 6f77a176f7
1 changed files with 94 additions and 69 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

163
documentation/adt-manual/adt-prepare.xml
View File

@ -231,7 +231,7 @@
<para> <para>
If you want to simply install the cross-toolchain by hand, you can If you want to simply install the cross-toolchain by hand, you can
do so by running the toolchain installer. do so by running the toolchain installer.
If you use this method to install the cross-toolchain and you If you use this method to install the cross-toolchain, you
might still need to install the target sysroot by installing and might still need to install the target sysroot by installing and
extracting it separately. extracting it separately.
For information on how to install the sysroot, see the For information on how to install the sysroot, see the
@ -241,82 +241,56 @@
<para> <para>
Follow these steps: Follow these steps:
<orderedlist> <orderedlist>
<listitem><para>Go to <listitem><para>Get the toolchain installer using one of the
<ulink url='&YOCTO_TOOLCHAIN_DL_URL;'></ulink> following methods:
and find the folder that matches your host development system <itemizedlist>
(i.e. <filename>i686</filename> for 32-bit machines or <listitem><para>Go to
<filename>x86-64</filename> for 64-bit machines).</para></listitem> <ulink url='&YOCTO_TOOLCHAIN_DL_URL;'></ulink>
<listitem><para>Go into that folder and download the toolchain installer whose name and find the folder that matches your host
includes the appropriate target architecture. development system (i.e. <filename>i686</filename>
For example, if your host development system is an Intel-based 64-bit system and for 32-bit machines or <filename>x86-64</filename>
you are going to use your cross-toolchain for an Intel-based 32-bit target, go into the for 64-bit machines).</para>
<filename>x86_64</filename> folder and download the following installer: <para>Go into that folder and download the toolchain
<literallayout class='monospaced'> installer whose name includes the appropriate target
architecture.
For example, if your host development system is an
Intel-based 64-bit system and you are going to use
your cross-toolchain for an Intel-based 32-bit
target, go into the <filename>x86_64</filename>
folder and download the following installer:
<literallayout class='monospaced'>
poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.sh poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.sh
</literallayout> </literallayout></para></listitem>
<note><para>As an alternative to steps one and two, you can <listitem><para>Build your own toolchain installer.
build the toolchain installer if you have a For cases where you cannot use an installer
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>. from the download area, you can build your as
If you need GMAE, you should use the described in the
<filename>bitbake meta-toolchain-gmae</filename> "<link linkend='optionally-building-a-toolchain-installer'>Optionally Building a Toolchain Installer</link>"
command. section.</para></listitem>
Running the resulting installation script will support </itemizedlist></para></listitem>
such development. <listitem><para>Once you have the installer, run it to install
If you are not concerned with GMAE, you can generate the toolchain.
the toolchain installer using
<filename>bitbake meta-toolchain</filename>.
Either of these methods requires you to still
install the target sysroot by installing and
extracting it separately.
For information on how to install the sysroot, see the
"<link linkend='extracting-the-root-filesystem'>Extracting the Root Filesystem</link>" section.
</para>
<para>A final method of building the toolchain installer
exists that has significant advantages over the previous
two methods.
This method results in a toolchain installer that
contains the sysroot that matches your target root
filesystem.
To build this installer, use the
<filename>bitbake image -c populate_sdk</filename>
command.</para>
<para>Remember, before using any
<filename>bitbake</filename> command, you must source
the <filename>&OE_INIT_PATH;</filename> script
located in the Source Directory and you must make sure
your <filename>conf/local.conf</filename> variables are
correct.
In particular, you need to be sure the
<ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink>
variable matches the architecture for which you are
building and that the
<ulink url='&YOCTO_DOCS_REF_URL;#var-SDKMACHINE'><filename>SDKMACHINE</filename></ulink>
variable is correctly set if you are building
a toolchain designed to run on an architecture that
differs from your current development host machine
(i.e. the build machine).</para>
<para>When the BitBake command
completes, the toolchain installer will be in
<filename>tmp/deploy/sdk</filename> in the Build
Directory.</para>
</note></para></listitem>
<listitem><para>Once you have the installer, run it to install the toolchain.
You must change the permissions on the toolchain installer You must change the permissions on the toolchain installer
script so that it is executable.</para> script so that it is executable.</para>
<para>The following command shows how to run the installer given a toolchain tarball <para>The following command shows how to run the installer
for a 64-bit development host system and a 32-bit target architecture. given a toolchain tarball for a 64-bit development host
The example assumes the toolchain installer is located in <filename>~/Downloads/</filename>. system and a 32-bit target architecture.
The example assumes the toolchain installer is located
in <filename>~/Downloads/</filename>.
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ ~/Downloads/poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.sh $ ~/Downloads/poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.sh
</literallayout> </literallayout>
<note> <note>
If you do not have write permissions for the directory into which you are installing If you do not have write permissions for the directory
the toolchain, the toolchain installer notifies you and exits. into which you are installing the toolchain, the
Be sure you have write permissions in the directory and run the installer again. toolchain installer notifies you and exits.
Be sure you have write permissions in the directory and
run the installer again.
</note> </note>
Once the tarball is expanded, the cross-toolchain is installed. Once the tarball is expanded, the cross-toolchain is
You will notice environment setup files for the cross-toolchain in the directory. installed.
</para></listitem> You will notice environment setup files for the
cross-toolchain in the directory.</para></listitem>
</orderedlist> </orderedlist>
</para> </para>
</section> </section>
@ -539,6 +513,57 @@
</section> </section>
</section> </section>
<section id='optionally-building-a-toolchain-installer'>
<title>Optionally Building a Toolchain Installer</title>
<para>
As an alternative to locating and downloading a toolchain installer,
you can build the toolchain installer if you have a
<ulink url='&YOCTO_DOCS_DEV_URL;#build-directory'>Build Directory</ulink>.
</para>
<para>
If you need GMAE, you should use the
<filename>bitbake meta-toolchain-gmae</filename> command.
Running the resulting installation script will support such development.
If you are not concerned with GMAE, you can build the toolchain
installer using <filename>bitbake meta-toolchain</filename>.
Either of these methods requires you to still install the target
sysroot by installing and extracting it separately.
For information on how to install the sysroot, see the
"<link linkend='extracting-the-root-filesystem'>Extracting the Root Filesystem</link>" section.
</para>
<para>
A final method of building the toolchain installer exists that has
significant advantages over the previous two methods.
This method results in a toolchain installer that contains the sysroot
that matches your target root filesystem.
To build this installer, use the
<filename>bitbake image -c populate_sdk</filename> command.
</para>
<para>
Remember, before using any <filename>bitbake</filename> command, you
must source the <filename>&OE_INIT_PATH;</filename> script located in
the Source Directory and you must make sure your
<filename>conf/local.conf</filename> variables are correct.
In particular, you need to be sure the
<ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink>
variable matches the architecture for which you are building and that
the
<ulink url='&YOCTO_DOCS_REF_URL;#var-SDKMACHINE'><filename>SDKMACHINE</filename></ulink>
variable is correctly set if you are building a toolchain designed to
run on an architecture that differs from your current development host
machine (i.e. the build machine).
</para>
<para>
When the BitBake command completes, the toolchain installer will be in
<filename>tmp/deploy/sdk</filename> in the Build Directory.
</para>
</section>
</chapter> </chapter>
<!-- <!--
vim: expandtab tw=80 ts=4 vim: expandtab tw=80 ts=4