2011-03-14 20:19:44 +00:00
< !DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
2011-03-14 21:27:51 +00:00
<chapter id= 'adt-prepare' >
2011-03-14 20:19:44 +00:00
2011-03-14 23:47:21 +00:00
<title > Preparing to Use the Application Development Toolkit (ADT)</title>
2011-03-14 20:19:44 +00:00
2011-03-14 23:47:21 +00:00
<para >
2011-09-01 16:18:33 +00:00
In order to use the ADT, you must install it, <filename > source</filename> a script to set up the
environment, and be sure both the kernel and filesystem image specific to the target architecture
exist.
2011-09-15 13:15:35 +00:00
This chapter describes how to be sure you meet the ADT requirements.
2011-06-23 14:24:43 +00:00
</para>
2011-03-14 23:47:21 +00:00
<section id= 'installing-the-adt' >
<title > Installing the ADT</title>
2011-06-23 14:24:43 +00:00
2011-03-14 20:19:44 +00:00
<para >
2011-06-23 14:24:43 +00:00
The following list describes how you can install the ADT, which includes the cross-toolchain.
2011-09-01 16:18:33 +00:00
Regardless of the installation you choose, you must <filename > source</filename> the cross-toolchain
2011-06-23 14:24:43 +00:00
environment setup script before you use the toolchain.
2011-09-15 19:51:05 +00:00
See the "<link linkend= 'setting-up-the-cross-development-environment' > Setting Up the
Cross-Development Environment</link> "
2011-06-23 14:24:43 +00:00
section for more information.
<itemizedlist >
<listitem > <para > <emphasis > Use the ADT Installer Script:</emphasis>
2011-09-01 16:18:33 +00:00
This method is the recommended way to install the ADT because it
automates much of the process for you.
For example, you can configure the installation to install the QEMU emulator
and the user-space NFS, specify which root filesystem profiles to download,
and define the target sysroot location.</para> </listitem>
2011-06-23 14:24:43 +00:00
<listitem > <para > <emphasis > Use an Existing Toolchain Tarball:</emphasis>
2011-09-01 16:18:33 +00:00
Using this method, you select and download an architecture-specific
toolchain tarball and then hand-install the toolchain.
If you use this method, you just get the cross-toolchain and QEMU - you do not
get any of the other mentioned benefits had you run the ADT Installer script.</para> </listitem>
2011-08-15 14:38:02 +00:00
<listitem > <para > <emphasis > Use the Toolchain from within a Yocto Project Build Tree:</emphasis>
2011-09-15 19:12:06 +00:00
If you already have a Yocto Project build tree, you can build the cross-toolchain
within tree.
2011-09-01 16:18:33 +00:00
However, like the previous method mentioned, you only get the cross-toolchain and QEMU - you
do not get any of the other benefits without taking separate steps.</para> </listitem>
2011-06-23 14:24:43 +00:00
</itemizedlist>
2011-03-14 20:19:44 +00:00
</para>
2011-03-14 23:47:21 +00:00
2011-06-23 14:24:43 +00:00
<section id= 'using-the-adt-installer' >
<title > Using the ADT Installer</title>
2011-03-14 23:47:21 +00:00
<para >
2011-08-15 14:38:02 +00:00
To run the ADT Installer, you need to first get the ADT Installer tarball and then run the ADT
2011-06-23 14:24:43 +00:00
Installer Script.
2011-03-14 20:19:44 +00:00
</para>
2011-06-23 14:24:43 +00:00
<section id= 'getting-the-adt-installer-tarball' >
<title > Getting the ADT Installer Tarball</title>
2011-03-14 23:47:21 +00:00
2011-06-23 14:24:43 +00:00
<para >
The ADT Installer is contained in the ADT Installer tarball.
2012-01-13 14:12:39 +00:00
You can download the tarball into any directory from the
<ulink url= 'http://downloads.yoctoproject.org/releases' > Index of Releases</ulink> , specifically
at
2012-01-06 22:10:46 +00:00
<ulink url= 'http://downloads.yoctoproject.org/releases/yocto/yocto-1.1.1/adt_installer' > </ulink> .
2011-09-01 16:18:33 +00:00
Or, you can use BitBake to generate the tarball inside the existing Yocto Project
build tree.
2011-06-23 14:24:43 +00:00
</para>
<para >
2011-07-14 14:00:42 +00:00
If you use BitBake to generate the ADT Installer tarball, you must
2011-09-15 19:12:06 +00:00
<filename > source</filename> the Yocto Project environment setup script
(<filename > oe-init-build-env</filename> ) located
2011-09-01 16:18:33 +00:00
in the Yocto Project file structure before running the <filename > bitbake</filename>
command that creates the tarball.
2011-06-23 14:24:43 +00:00
</para>
<para >
2011-08-15 14:38:02 +00:00
The following example commands download the Yocto Project release tarball, set up the Yocto
2011-09-01 16:18:33 +00:00
Project files structure, set up the environment while also creating the
default Yocto Project build tree,
and run the <filename > bitbake</filename> command that results in the tarball
2011-06-23 14:24:43 +00:00
<filename > ~/yocto-project/build/tmp/deploy/sdk/adt_installer.tar.bz2</filename> :
<literallayout class= 'monospaced' >
$ cd ~
$ mkdir yocto-project
$ cd yocto-project
2012-01-06 22:10:46 +00:00
$ wget http://downloads.yoctoproject.org/releases/yocto/yocto-1.1.1/poky-edison-6.0.1.tar.bz2
2012-01-13 01:02:18 +00:00
$ tar xjf poky-edison-6.0.1.tar.bz2
$ source poky-edison-6.0.1/oe-init-build-env
2011-06-23 14:24:43 +00:00
$ bitbake adt-installer
</literallayout>
</para>
</section>
<section id= 'configuring-and-running-the-adt-installer-script' >
<title > Configuring and Running the ADT Installer Script</title>
<para >
2011-08-15 14:38:02 +00:00
Before running the ADT Installer script, you need to unpack the tarball.
2011-06-23 14:24:43 +00:00
You can unpack the tarball in any directory you wish.
2012-01-13 15:02:31 +00:00
For example, this command copies the ADT Installer tarball from where
it was built into the home directory and then unpacks the tarball into
a top-level directory named <filename > adt-installer</filename> :
<literallayout class= 'monospaced' >
$ cd ~
2012-01-19 18:52:27 +00:00
$ cp ~/yocto-project/build/tmp/deploy/sdk/adt_installer.tar.bz2 $HOME
2012-01-13 15:02:31 +00:00
$ tar -xjf adt_installer.tar.bz2
</literallayout>
2011-06-23 14:24:43 +00:00
Unpacking it creates the directory <filename > adt-installer</filename> ,
2011-09-02 18:51:55 +00:00
which contains the ADT Installer script (<filename > adt_installer</filename> )
and its configuration file (<filename > adt_installer.conf</filename> ).
2011-06-23 14:24:43 +00:00
</para>
<para >
Before you run the script, however, you should examine the ADT Installer configuration
2011-09-02 18:51:55 +00:00
file and be sure you are going to get what you want.
2011-06-23 14:24:43 +00:00
Your configurations determine which kernel and filesystem image are downloaded.
</para>
<para >
The following list describes the configurations you can define for the ADT Installer.
2011-09-01 16:18:33 +00:00
For configuration values and restrictions, see the comments in
2011-06-23 14:24:43 +00:00
the <filename > adt-installer.conf</filename> file:
<itemizedlist >
2011-09-02 18:51:55 +00:00
<listitem > <para > <filename > YOCTOADT_REPO</filename> : This area
2011-09-01 16:18:33 +00:00
includes the IPKG-based packages and the root filesystem upon which
the installation is based.
If you want to set up your own IPKG repository pointed to by
2011-09-02 18:51:55 +00:00
<filename > YOCTOADT_REPO</filename> , you need to be sure that the
2011-09-01 16:18:33 +00:00
directory structure follows the same layout as the reference directory
set up at <ulink url= 'http://adtrepo.yoctoproject.org' > </ulink> .
Also, your repository needs to be accessible through HTTP.</para> </listitem>
2011-09-02 18:51:55 +00:00
<listitem > <para > <filename > YOCTOADT_TARGETS</filename> : The machine
2011-09-01 16:18:33 +00:00
target architectures for which you want to set up cross-development
environments.</para> </listitem>
<listitem > <para > <filename > YOCTOADT_QEMU</filename> : Indicates whether
or not to install the emulator QEMU.</para> </listitem>
<listitem > <para > <filename > YOCTOADT_NFS_UTIL</filename> : Indicates whether
or not to install user-mode NFS.
If you plan to use the Yocto Eclipse IDE plug-in against QEMU,
you should install NFS.
<note > To boot QEMU images using our userspace NFS server, you need
to be running <filename > portmap</filename> or <filename > rpcbind</filename> .
If you are running <filename > rpcbind</filename> , you will also need to add the
<filename > -i</filename> option when <filename > rpcbind</filename> starts up.
Please make sure you understand the security implications of doing this.
You might also have to modify your firewall settings to allow
NFS booting to work.</note> </para> </listitem>
<listitem > <para > <filename > YOCTOADT_ROOTFS_< arch> </filename> : The root
filesystem images you want to download from the
<filename > YOCTOADT_IPKG_REPO</filename> repository.</para> </listitem>
<listitem > <para > <filename > YOCTOADT_TARGET_SYSROOT_IMAGE_< arch> </filename> : The
particular root filesystem used to extract and create the target sysroot.
The value of this variable must have been specified with
<filename > YOCTOADT_ROOTFS_< arch> </filename> .
For example, if you downloaded both <filename > minimal</filename> and
<filename > sato-sdk</filename> images by setting
<filename > YOCTOADT_ROOTFS_< arch> </filename>
to "minimal sato-sdk", then <filename > YOCTOADT_ROOTFS_< arch> </filename>
must be set to either <filename > minimal</filename> or
<filename > sato-sdk</filename> .</para> </listitem>
<listitem > <para > <filename > YOCTOADT_TARGET_SYSROOT_LOC_< arch> </filename> : The
location on the development host where the target sysroot is created.
</para> </listitem>
2011-06-23 14:24:43 +00:00
</itemizedlist>
</para>
2011-03-14 23:47:21 +00:00
2011-06-23 14:24:43 +00:00
<para >
After you have configured the <filename > adt_installer.conf</filename> file,
2012-01-19 18:52:27 +00:00
run the installer for this example using the following commands:
2011-06-23 14:24:43 +00:00
<literallayout class= 'monospaced' >
2012-01-19 18:52:27 +00:00
$ cd ~/adt-installer
$ ./adt_installer
2011-06-23 14:24:43 +00:00
</literallayout>
</para>
2011-03-14 23:47:21 +00:00
2011-06-23 14:24:43 +00:00
<note >
The ADT Installer requires the <filename > libtool</filename> package to complete.
If you install the recommended packages as described in the
2012-01-03 20:46:31 +00:00
"<ulink url= 'http://www.yoctoproject.org/docs/1.1.1/yocto-project-qs/yocto-project-qs.html#packages' > Packages</ulink> "
2011-09-15 12:52:25 +00:00
section of
2012-01-03 20:46:31 +00:00
<ulink url= 'http://www.yoctoproject.org/docs/1.1.1/yocto-project-qs/yocto-project-qs.html' >
2011-09-01 16:18:33 +00:00
The Yocto Project Quick Start</ulink> , then you will have libtool installed.
2011-06-23 14:24:43 +00:00
</note>
2011-03-14 20:19:44 +00:00
2011-06-23 14:24:43 +00:00
<para >
2011-08-15 14:38:02 +00:00
Once the installer begins to run, you are asked whether you want to run in
2011-06-23 14:24:43 +00:00
interactive or silent mode.
2011-09-01 16:18:33 +00:00
If you want to closely monitor the installation, choose “I” for interactive
2011-06-23 14:24:43 +00:00
mode rather than “S” for silent mode.
Follow the prompts from the script to complete the installation.
</para>
2011-03-14 20:19:44 +00:00
2011-06-23 14:24:43 +00:00
<para >
Once the installation completes, the ADT, which includes the cross-toolchain, is installed.
You will notice environment setup files for the cross-toolchain in
2012-01-04 13:52:32 +00:00
<filename > /opt/poky/1.1.1</filename> ,
2011-06-23 14:24:43 +00:00
and image tarballs in the <filename > adt-installer</filename>
directory according to your installer configurations, and the target sysroot located
according to the <filename > YOCTOADT_TARGET_SYSROOT_LOC_< arch> </filename> variable
also in your configuration file.
</para>
2011-09-01 16:18:33 +00:00
</section>
2011-03-14 23:47:21 +00:00
</section>
2011-03-14 20:19:44 +00:00
2011-03-14 23:47:21 +00:00
<section id= 'using-an-existing-toolchain-tarball' >
2011-06-23 14:24:43 +00:00
<title > Using a Cross-Toolchain Tarball</title>
2011-09-01 16:18:33 +00:00
2011-06-23 14:24:43 +00:00
<para >
2011-08-15 14:38:02 +00:00
If you want to simply install the cross-toolchain by hand, you can do so by using an existing
2011-06-23 14:24:43 +00:00
cross-toolchain tarball.
2011-09-15 17:17:08 +00:00
If you use this method to install the cross-toolchain and you still need to install the target
sysroot, you will have to install sysroot separately.
2011-06-23 14:24:43 +00:00
</para>
2011-03-14 23:47:21 +00:00
<para >
Follow these steps:
<orderedlist >
2011-06-23 14:24:43 +00:00
<listitem > <para > Go to
2012-01-19 18:52:27 +00:00
<ulink url= 'http://downloads.yoctoproject.org/releases/yocto/yocto-1.1.1/toolchain' > </ulink>
2011-09-01 16:18:33 +00:00
and find the folder that matches your host development system
2012-01-19 18:52:27 +00:00
(i.e. <filename > i686</filename> for 32-bit machines or
2011-09-01 16:18:33 +00:00
<filename > x86_64</filename> for 64-bit machines).</para> </listitem>
2011-06-23 14:24:43 +00:00
<listitem > <para > Go into that folder and download the toolchain tarball whose name
2011-09-01 16:18:33 +00:00
includes the appropriate target architecture.
For example, if your host development system is an Intel-based 64-bit system and
2011-09-15 19:12:06 +00:00
you are going to use your cross-toolchain for an Intel-based 32-bit target, go into the
2011-09-01 16:18:33 +00:00
<filename > x86_64</filename> folder and download the following tarball:
<literallayout class= 'monospaced' >
2012-01-19 18:52:27 +00:00
poky-eglibc-x86_64-i586-toolchain-1.1.1.tar.bz2
2011-10-03 19:07:21 +00:00
</literallayout>
2011-09-15 17:17:08 +00:00
<note > <para > As an alternative to steps one and two, you can build the toolchain tarball
2011-09-02 18:51:55 +00:00
if you have a Yocto Project build tree.
2011-09-15 17:17:08 +00:00
If you need GMAE, you should use the <filename > bitbake meta-toolchain-gmae</filename>
command.
The resulting tarball will support such development.
2011-09-15 19:12:06 +00:00
However, if you are not concerned with GMAE,
2011-09-15 17:17:08 +00:00
you can generate the tarball using <filename > bitbake meta-toolchain</filename> .</para>
<para > Use the appropriate <filename > bitbake</filename> command only after you have
2011-09-15 19:12:06 +00:00
sourced the <filename > oe-build-init-env</filename> script located in the Yocto
2011-09-01 16:18:33 +00:00
Project files.
2011-09-15 19:12:06 +00:00
When the <filename > bitbake</filename> command completes, the tarball will
2011-09-01 16:18:33 +00:00
be in <filename > tmp/deploy/sdk</filename> in the Yocto Project build tree.
2011-09-15 17:17:08 +00:00
</para> </note> </para> </listitem>
2011-09-02 18:51:55 +00:00
<listitem > <para > Make sure you are in the root directory with root privileges and then expand
2011-09-01 16:18:33 +00:00
the tarball.
2012-01-04 13:52:32 +00:00
The tarball expands into <filename > /opt/poky/1.1.1</filename> .
2011-09-15 19:12:06 +00:00
Once the tarball is expanded, the cross-toolchain is installed.
2011-09-01 16:18:33 +00:00
You will notice environment setup files for the cross-toolchain in the directory.
2012-01-19 18:52:27 +00:00
Here is an example where the tarball exists in the user's <filename > Downloads</filename>
directory:
<literallayout class= 'monospaced' >
# cd /
# tar -xjf /home/scottrif/Downloads/poky-eglibc-x86_64-i586-toolchain-gmae-1.1.tar.bz2
</literallayout>
2011-09-01 16:18:33 +00:00
</para> </listitem>
2011-03-14 23:47:21 +00:00
</orderedlist>
</para>
</section>
2011-03-14 20:19:44 +00:00
2011-03-14 23:47:21 +00:00
<section id= 'using-the-toolchain-from-within-the-build-tree' >
2011-07-14 14:00:42 +00:00
<title > Using BitBake and the Yocto Project Build Tree</title>
2011-09-01 16:18:33 +00:00
2011-03-14 23:47:21 +00:00
<para >
2011-09-15 19:12:06 +00:00
A final way of installing just the cross-toolchain is to use BitBake to build the
toolchain within an existing Yocto Project build tree.
This method does not install the toolchain into the <filename > /opt</filename> directory.
2011-09-15 17:17:08 +00:00
As with the previous method, if you need to install the target sysroot, you must
do this separately.
</para>
<para >
2011-09-15 19:12:06 +00:00
Follow these steps to build and install the toolchain into the build tree:
2011-06-23 14:24:43 +00:00
<orderedlist >
2011-09-15 19:12:06 +00:00
<listitem > <para > Source the environment setup script
<filename > oe-init-build-env</filename> located in the Yocto Project
files.</para> </listitem>
2011-09-01 16:18:33 +00:00
<listitem > <para > At this point, you should be sure that the
<filename > MACHINE</filename> variable
2011-10-03 19:07:21 +00:00
in the <filename > local.conf</filename> file found in the
<filename > conf</filename> directory of the Yocto Project build directory
2011-09-01 16:18:33 +00:00
is set for the target architecture.
Comments within the <filename > local.conf</filename> file list the values you
can use for the <filename > MACHINE</filename> variable.
<note > You can populate the build tree with the cross-toolchains for more
than a single architecture.
You just need to edit the <filename > MACHINE</filename> variable in the
<filename > local.conf</filename> file and re-run the BitBake
command.</note> </para> </listitem>
2011-06-23 14:24:43 +00:00
<listitem > <para > Run <filename > bitbake meta-ide-support</filename> to complete the
2011-09-01 16:18:33 +00:00
cross-toolchain installation.
2012-01-19 18:52:27 +00:00
<note > If you change out of your working directory after you
2011-09-01 16:18:33 +00:00
<filename > source</filename> the environment setup script and before you run
2011-10-03 19:07:21 +00:00
the <filename > bitbake</filename> command, the command might not work.
2011-09-01 16:18:33 +00:00
Be sure to run the <filename > bitbake</filename> command immediately
after checking or editing the <filename > local.conf</filename> but without
2011-09-15 19:12:06 +00:00
changing out of your working directory.</note>
2011-10-03 19:07:21 +00:00
Once the <filename > bitbake</filename> command finishes,
the tarball for the cross-toolchain is generated within the Yocto Project build tree.
2011-09-01 16:18:33 +00:00
You will notice environment setup files for the cross-toolchain in the
Yocto Project build tree in the <filename > tmp</filename> directory.
Setup script filenames contain the strings <filename > environment-setup</filename> .
</para> </listitem>
2011-06-23 14:24:43 +00:00
</orderedlist>
2011-03-14 23:47:21 +00:00
</para>
</section>
</section>
2011-09-15 19:12:06 +00:00
<section id= 'setting-up-the-cross-development-environment' >
<title > Setting Up the Cross-Development Environment</title>
2011-09-01 16:18:33 +00:00
2011-03-14 23:47:21 +00:00
<para >
2011-09-15 19:12:06 +00:00
Before you can develop using the cross-toolchain, you need to set up the
2011-10-03 19:07:21 +00:00
cross-development environment by sourcing the toolchain's environment setup script.
2011-06-23 14:44:29 +00:00
If you used the ADT Installer or used an existing ADT tarball to install the ADT,
2012-01-04 13:52:32 +00:00
then you can find this script in the <filename > /opt/poky/1.1.1</filename>
2011-03-14 23:47:21 +00:00
directory.
2011-09-15 17:17:08 +00:00
If you installed the toolchain in the build tree, you can find the environment setup
2011-10-03 19:07:21 +00:00
script for the toolchain in the Yocto Project build tree's <filename > tmp</filename> directory.
2011-03-14 23:47:21 +00:00
</para>
<para >
2012-01-19 18:52:27 +00:00
Be sure to source the environment setup script that matches the architecture for
2011-03-14 23:47:21 +00:00
which you are developing.
2011-09-01 16:18:33 +00:00
Environment setup scripts begin with the string “<filename > environment-setup</filename> ”
and include as part of their name the architecture.
2012-01-19 18:52:27 +00:00
For example, the command to source the toolchain environment setup script
for a 64-bit IA-based machine would be the following:
2011-03-14 23:47:21 +00:00
<literallayout class= 'monospaced' >
2012-01-19 18:52:27 +00:00
$ source /opt/poky/1.1.1/environment-setup-x86_64-poky-linux
2011-03-14 23:47:21 +00:00
</literallayout>
</para>
</section>
2011-09-15 17:42:21 +00:00
<section id= 'securing-kernel-and-filesystem-images' >
<title > Securing Kernel and Filesystem Images</title>
2011-09-01 16:18:33 +00:00
2011-03-14 23:47:21 +00:00
<para >
You will need to have a kernel and filesystem image to boot using your
2011-09-15 17:17:08 +00:00
hardware or the QEMU emulator.
Furthermore, if you plan on booting your image using NFS or you want to use the root filesystem
as the target sysroot, you need to extract the root filesystem.
</para>
<section id= 'getting-the-images' >
<title > Getting the Images</title>
<para >
2011-09-15 19:12:06 +00:00
To get the kernel and filesystem images, you either have to build them or download
2011-09-15 17:17:08 +00:00
pre-built versions.
You can find examples for both these situations in the
2012-01-03 20:46:31 +00:00
"<ulink url= 'http://www.yoctoproject.org/docs/1.1.1/yocto-project-qs/yocto-project-qs.html#test-run' > A
2012-01-19 18:52:27 +00:00
Quick Test Run</ulink> " section of The Yocto Project Quick Start.
2011-09-30 15:34:48 +00:00
</para>
<para >
2011-09-15 17:17:08 +00:00
The Yocto Project provides basic kernel and filesystem images for several
2011-08-15 14:38:02 +00:00
architectures (<filename > x86</filename> , <filename > x86-64</filename> ,
<filename > mips</filename> , <filename > powerpc</filename> , and <filename > arm</filename> )
that you can use unaltered in the QEMU emulator.
2011-09-15 17:17:08 +00:00
These kernel images reside in the Yocto Project release
2012-01-19 18:52:27 +00:00
area - <ulink url= 'http://downloads.yoctoproject.org/releases/yocto/yocto-1.1.1/machines/' > </ulink>
2011-09-30 15:34:48 +00:00
and are ideal for experimentation within Yocto Project.
For information on the image types you can build using the Yocto Project, see the
2012-01-19 18:52:27 +00:00
"<ulink url= 'http://www.yoctoproject.org/docs/1.1.1/poky-ref-manual/poky-ref-manual.html#ref-images' > Reference: Images</ulink> " appendix in The Yocto Project Reference Manual.
2011-09-30 15:34:48 +00:00
</para>
<para >
If you plan on remotely deploying and debugging your application from within the
Eclipse IDE, you must have an image that contains the Yocto Target Communication
Framework (TCF) agent (<filename > tcf-agent</filename> ).
2011-09-30 16:02:18 +00:00
By default, the Yocto Project provides only one type pre-built image that contains the
2011-09-30 15:34:48 +00:00
<filename > tcf-agent</filename> .
2011-09-30 16:02:18 +00:00
And, those images are SDK (e.g.<filename > core-image-sato-sdk</filename> ).
2011-09-30 15:34:48 +00:00
</para>
<para >
If you want to use a different image type that contains the <filename > tcf-agent</filename> ,
you can do so one of two ways:
<itemizedlist >
2012-01-19 18:52:27 +00:00
<listitem > <para > Modify the <filename > conf/local.conf</filename> configuration file in
2011-09-30 15:34:48 +00:00
the Yocto Project build directory and then rebuild the image.
2011-09-30 16:02:18 +00:00
With this method, you need to modify the <filename > EXTRA_IMAGE_FEATURES</filename>
2011-09-30 15:34:48 +00:00
variable to have the value of "tools-debug" before rebuilding the image.
Once the image is rebuilt, the <filename > tcf-agent</filename> will be included
in the image and is launched automatically after the boot.</para> </listitem>
<listitem > <para > Manually build the <filename > tcf-agent</filename> .
To build the agent, follow these steps:
<orderedlist >
<listitem > <para > Be sure the ADT is installed as described in the
"<link linkend= 'installing-the-adt' > Installing the ADT</link> " section.
</para> </listitem>
<listitem > <para > Set up the cross-development environment as described in the
"<link linkend= 'setting-up-the-cross-development-environment' > Setting
Up the Cross-Development Environment</link> " section.</para> </listitem>
<listitem > <para > Get the <filename > tcf-agent</filename> source code, which is
stored using the Subversion SCM, using the following command:
<literallayout class= 'monospaced' >
$ svn checkout svn://dev.eclipse.org/svnroot/dsdp/org.eclipse.tm.tcf/trunk/agent \
< -r #rev_number>
</literallayout> </para> </listitem>
<listitem > <para > Modify the <filename > Makefile.inc</filename> file
for the cross-compilation environment by setting the
<filename > OPSYS</filename> and <filename > MACHINE</filename>
variables according to your target.</para> </listitem>
<listitem > <para > Use the cross-development tools to build the
<filename > tcf-agent</filename> .
Before you "Make" the file, be sure your cross-tools are set up first.
See the "<link linkend= 'makefile-based-projects' > Makefile-Based Projects</link> "
section for information on how to make sure the cross-tools are set up
correctly.</para>
<para > If the build is successful, the <filename > tcf-agent</filename> output will
be <filename > obj/$(OPSYS)/$(MACHINE)/Debug/agent</filename> .</para> </listitem>
<listitem > <para > Deploy the agent into the image's root filesystem.</para> </listitem>
</orderedlist>
</para> </listitem>
</itemizedlist>
2011-09-15 17:17:08 +00:00
</para>
</section>
2011-09-15 12:52:25 +00:00
2011-09-15 17:17:08 +00:00
<section id= 'extracting-the-root-filesystem' >
<title > Extracting the Root Filesystem</title>
<para >
2011-09-15 19:12:06 +00:00
You must extract the root filesystem if you want to boot the image using NFS
or you want to use the root filesystem as the target sysroot.
2011-09-15 17:17:08 +00:00
For example, the Eclipse IDE environment with the Eclipse Yocto Plug-in installed allows you
2011-09-15 19:12:06 +00:00
to use QEMU to boot under NFS.
Another example is if you want to develop your target application using the
2011-09-15 17:17:08 +00:00
root filesystem as the target sysroot.
</para>
<para >
2011-09-15 19:12:06 +00:00
To extract the root filesystem, first <filename > source</filename>
the cross-development environment setup script and then
use the <filename > runqemu-extract-sdk</filename> command on the
2012-01-19 18:52:27 +00:00
filesystem image tarball.
For example, the following commands set up the environment by sourcing
the setup script from within the build directory and then extracting
2011-09-15 19:12:06 +00:00
the root filesystem from a previously built filesystem image tarball named
2012-01-19 18:52:27 +00:00
<filename > core-image-sato-sdk-qemux86.tar.bz2</filename> .
2011-09-15 17:17:08 +00:00
The example extracts the root filesystem into the <filename > $HOME/qemux86-sato</filename>
directory:
<literallayout class= 'monospaced' >
2011-09-15 19:12:06 +00:00
$ source $HOME/poky/build/tmp/environment-setup-i586-poky-linux
2011-09-15 17:17:08 +00:00
$ runqemu-extract-sdk \
2012-01-19 18:52:27 +00:00
tmp/deploy/images/core-image-sato-sdk-qemux86.tar.bz2 \
2011-09-15 17:17:08 +00:00
$HOME/qemux86-sato
</literallayout>
In this case, you could now point to the target sysroot at
<filename > $HOME/qemux86-sato</filename> .
</para>
</section>
2011-03-14 23:47:21 +00:00
</section>
2011-03-14 20:19:44 +00:00
</chapter>
<!--
vim: expandtab tw=80 ts=4
-->