1 files changed, 149 insertions, 0 deletions

diff --git a/documentation/book-enea-linux-users-guide/doc/install_toolchain.xml b/documentation/book-enea-linux-users-guide/doc/install_toolchain.xml
new file mode 100644
index 0000000..d5f7254
--- /dev/null
+++ b/documentation/book-enea-linux-users-guide/doc/install_toolchain.xml
@@ -0,0 +1,149 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<section id="enea-linux-install-cc-toolchain">
+  <title>Install the Cross-Compilation Toolchain</title>
+
+  <para>Before cross-compiling<indexterm>
+      <primary>cross-compiling</primary>
+    </indexterm> applications for your target, you need to install the
+  Software Development Kit (SDK<indexterm>
+      <primary>SDK</primary>
+    </indexterm>) - which contains the cross-compilation toolchain<indexterm>
+      <primary>toolchain</primary>
+    </indexterm> - and set up the cross-compilation environment on your host.
+  The toolchain for each supported target contains a 32-bit and a 64-bit
+  library for gcc. The toolchain and the environment-setup script are wrapped
+  together inside a toolchain installer in the form of a shell script.</para>
+
+  <simplelist>
+    <member>Name of the installer:</member>
+
+    <member><literal><xi:include href="../../docsrc_common/pardoc-distro.xml"
+    xmlns:xi="http://www.w3.org/2001/XInclude"
+    xpointer="element(EneaLinux_SDK_INSTALLER/1)" /></literal></member>
+  </simplelist>
+
+  <simplelist>
+    <member>Name of the environment-setup scripts:</member>
+
+    <member><literal><xi:include href="../../docsrc_common/pardoc-distro.xml"
+    xmlns:xi="http://www.w3.org/2001/XInclude"
+    xpointer="element(EneaLinux_SDK_ENV_SCRIPT_32/1)" /></literal></member>
+
+    <member><literal><xi:include href="../../docsrc_common/pardoc-distro.xml"
+    xmlns:xi="http://www.w3.org/2001/XInclude"
+    xpointer="element(EneaLinux_SDK_ENV_SCRIPT_64/1)" /></literal></member>
+  </simplelist>
+
+  <para>The cross-compilation toolchain for <literal>t4240rdb-64b</literal> is
+  packaged as follows:<itemizedlist spacing="compact">
+      <listitem>
+        <para>The toolchain contains two libs: <literal>lib</literal> (32-bit)
+        and <literal>lib64</literal> (64-bit).</para>
+      </listitem>
+
+      <listitem>
+        <para>The installer wraps two environment-setup scripts. Which script
+        you run selects which lib will be used by gcc. This way, both 32-bit
+        applications and 64-bit applications can be cross-compiled for
+        t4240rdb-64b.</para>
+
+        <note>
+          <para>There are currently problems with 32-bit applications on the
+          64-bit T4240, see "Known Problems" in the Release
+          Information.</para>
+        </note>
+      </listitem>
+    </itemizedlist>Do as in the example below to install the SDK and set up
+  the cross-compilation environment:</para>
+
+  <orderedlist>
+    <listitem>
+      <para>Get the cross-compilation toolchain installer; either a
+      precompiled one (A) or build it yourself (B).</para>
+
+      <orderedlist numeration="upperalpha">
+        <listitem>
+          <para>The quickest alternative is to use a precompiled installer for
+          your host and target. Download the appropriate installer from the
+          server appointed to you by Enea. You find the installer in the
+          <filename>sdk</filename> directory on the download site:</para>
+
+          <para><programlisting>$ wget <xi:include
+                href="../../docsrc_common/pardoc-distro.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude"
+                xpointer="element(ULINK_ENEA_LINUX_URL/1)" />/t4240-64b/sdk/\
+<xi:include href="../../docsrc_common/pardoc-distro.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude"
+                xpointer="element(EneaLinux_SDK_INSTALLER/1)" /></programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para>... or build your own cross-compilation toolchain. First
+          source the build environment setup script to create a
+          &lt;build_dir&gt; with conf files, then run bitbake with option
+          <literal>-c populate_sdk</literal> to build the toolchain and wrap
+          it inside an installer, saved in
+          <filename>&lt;build_dir&gt;/tmp/deploy/sdk/</filename>.</para>
+
+          <programlisting>$ source enea-init-build-env -b build_t4240rdb
+$ bitbake <xi:include href="../../docsrc_common/pardoc-distro.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude"
+              xpointer="element(EneaLinux_SDK_IMAGE/1)" /> -c populate_sdk
+$ cd ../build_t4240rdb/tmp/deploy/sdk/</programlisting>
+        </listitem>
+      </orderedlist>
+    </listitem>
+
+    <listitem>
+      <para>Run the installer to unpack the cross-compilation toolchain and
+      the environment-setup script:</para>
+
+      <programlisting>$ chmod 770 \
+    <xi:include href="../../docsrc_common/pardoc-distro.xml"
+          xmlns:xi="http://www.w3.org/2001/XInclude"
+          xpointer="element(EneaLinux_SDK_INSTALLER/1)" />
+$ ./<xi:include href="../../docsrc_common/pardoc-distro.xml"
+          xmlns:xi="http://www.w3.org/2001/XInclude"
+          xpointer="element(EneaLinux_SDK_INSTALLER/1)" /></programlisting>
+
+      <para>When prompted, select to install the SDK in the desired directory,
+      referred to as <literal>&lt;sdkdir&gt;</literal>, by default
+      <filename>/opt/enea/&lt;sdkver&gt;</filename>. The installer unpacks the
+      environment setup script in <filename>&lt;sdkdir&gt;</filename> and the
+      toolchain under <filename>&lt;sdkdir&gt;/sysroots</filename>.</para>
+
+      <note>
+        <para>Choose a unique directory for each toolchain. Installing a
+        second toolchain of any type (buildtools toolchain or
+        cross-compilation toolchain) in the same directory as a previously
+        installed one will break the $PATH variable of the first one.</para>
+      </note>
+    </listitem>
+
+    <listitem>
+      <para>Setup the toolchain environment by sourcing the environment-setup
+      script, here exemplified for 32-bit toolchain:<programlisting>$ source &lt;sdkdir&gt;/<xi:include
+            href="../../docsrc_common/pardoc-distro.xml"
+            xmlns:xi="http://www.w3.org/2001/XInclude"
+            xpointer="element(EneaLinux_SDK_ENV_SCRIPT_64/1)" /></programlisting></para>
+    </listitem>
+  </orderedlist>
+
+  <para>Once the cross-compilation toolchain is in place and the environment
+  set up, you can proceed with <link
+  linkend="enea-linux-cross-compile-from-command-line">Cross-Compiling
+  Applications from Command Line.</link>.</para>
+
+  <para>The above instructions and the files on the download site should
+  provide you with all you need to be able to cross-compile applications for
+  your target.</para>
+
+  <remark>INFO: Corresponding Yocto documentation is available at <xi:include
+  href="../../docsrc_common/pardoc-distro.xml"
+  xmlns:xi="http://www.w3.org/2001/XInclude"
+  xpointer="element(ULINK_YOCTO_ADT_TOOLCHAIN_URL/1)" />. Note that the file
+  names mentioned in the Yocto documentation differ from the ones in the Enea
+  Linux distribution.</remark>
+</section>
\ No newline at end of file