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-06-23 14:24:43 +00:00
|
|
|
|
In order to use the ADT you must install it, source a script to set up the
|
|
|
|
|
environment, and be sure the kernel and filesystem image specific to the target architecture
|
|
|
|
|
exists.
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>
|
|
|
|
|
This section describes how to be sure you meet these requirements.
|
|
|
|
|
Througout this section two important terms are used:
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem><para><emphasis>Yocto Project Source Tree:</emphasis>
|
|
|
|
|
This term refers to the directory structure created as a result of downloading
|
|
|
|
|
and unpacking a Yocto Project release tarball.
|
2011-07-14 14:00:42 +00:00
|
|
|
|
The Yocto Project source tree contains BitBake, Documentation, Meta-data and
|
2011-06-23 14:24:43 +00:00
|
|
|
|
other files.
|
|
|
|
|
The name of the top-level directory of the Yocto Project source tree
|
|
|
|
|
is derived from the Yocto Project release tarball.
|
|
|
|
|
For example, downloading and unpacking <filename>poky-bernard-5.0.1.tar.bz2</filename>
|
|
|
|
|
results in a Yocto Project source tree whose Yocto Project source directory is named
|
|
|
|
|
<filename>poky-bernard-5.0.1</filename>.</para></listitem>
|
|
|
|
|
<listitem><para><emphasis>Yocto Project Build Tree:</emphasis>
|
|
|
|
|
This term refers to the area where you run your builds.
|
|
|
|
|
The area is created when you source the Yocto Project setup environment script
|
|
|
|
|
that is found in the Yocto Project source directory
|
|
|
|
|
(e.g. <filename>poky-init-build-env</filename>).
|
|
|
|
|
You can create the Yocto Project build tree anywhere you want on your
|
|
|
|
|
development system.
|
|
|
|
|
Here is an example that creates the tree in <filename>mybuilds</filename>
|
|
|
|
|
and names the Yocto Project build directory <filename>YP-5.0.1</filename>:
|
|
|
|
|
<literallayout class='monospaced'>
|
|
|
|
|
$ source poky-bernard-5.0.1/poky-init-build-env $HOME/mybuilds/YP-5.0.1
|
|
|
|
|
</literallayout>
|
2011-07-14 14:00:42 +00:00
|
|
|
|
If you don't specifically name the build directory then BitBake creates it
|
2011-06-23 14:24:43 +00:00
|
|
|
|
in the current directory and uses the name <filename>build</filename>.
|
2011-07-14 14:00:42 +00:00
|
|
|
|
Also, if you supply an existing directory then BitBake uses that
|
2011-06-23 14:24:43 +00:00
|
|
|
|
directory as the Yocto Project build directory and populates the build tree
|
|
|
|
|
beneath it.</para></listitem>
|
|
|
|
|
</itemizedlist>
|
2011-03-14 23:47:21 +00:00
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<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.
|
|
|
|
|
Regardless of the installation you choose, however, you must source the cross-toolchain
|
|
|
|
|
environment setup script before you use the toolchain.
|
|
|
|
|
See the <xref linkend='setting-up-the-environment'>“Setting Up the Environment”</xref>
|
|
|
|
|
section for more information.
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem><para><emphasis>Use the ADT Installer Script:</emphasis>
|
|
|
|
|
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>
|
|
|
|
|
<listitem><para><emphasis>Use an Existing Toolchain Tarball:</emphasis>
|
|
|
|
|
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>
|
|
|
|
|
<listitem><para><emphasis>Use the Toolchain from Within a Yocto Project Build Tree:</emphasis>
|
|
|
|
|
If you already have a Yocto Project build tree you can install the cross-toolchain
|
|
|
|
|
using that tree.
|
|
|
|
|
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>
|
|
|
|
|
</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-06-23 14:24:43 +00:00
|
|
|
|
To run the ADT Installer you need to first get the ADT Installer tarball and then run the ADT
|
|
|
|
|
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.
|
|
|
|
|
You can download the tarball into any directory from
|
|
|
|
|
<ulink url='http://autobuilder.yoctoproject.org/downloads/yocto-1.0/adt-installer/'></ulink>.
|
2011-07-14 14:00:42 +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-06-23 14:24:43 +00:00
|
|
|
|
source the Yocto Project environment setup script located in the Yocto Project
|
2011-07-14 14:00:42 +00:00
|
|
|
|
source directory before running the BitBake command that creates the tarball.
|
2011-06-23 14:24:43 +00:00
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>
|
|
|
|
|
The following example commands download the Yocto Project release tarball, create the Yocto
|
|
|
|
|
Project source tree, set up the environment while also creating the Yocto Project build tree,
|
2011-07-14 14:00:42 +00:00
|
|
|
|
and finally run the BitBake 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
|
|
|
|
|
$ wget http://www.yoctoproject.org/downloads/poky/poky-bernard-5.0.1.tar.bz2
|
|
|
|
|
$ tar xjf poky-bernard-5.0.1.tar.bz2
|
|
|
|
|
$ source poky-bernard-5.0.1/poky-init-build-env poky-5.0.1-build
|
|
|
|
|
$ 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>
|
|
|
|
|
Before running the ADT Installer script you need to unpack the tarball.
|
|
|
|
|
You can unpack the tarball in any directory you wish.
|
|
|
|
|
Unpacking it creates the directory <filename>adt-installer</filename>,
|
|
|
|
|
which contains the ADT Installer script and its configuration file.
|
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>
|
|
|
|
|
Before you run the script, however, you should examine the ADT Installer configuration
|
|
|
|
|
file (<filename>adt_installer</filename>) and be sure you are going to get what you want.
|
|
|
|
|
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.
|
|
|
|
|
For configuration values and restrictions see the comments in
|
|
|
|
|
the <filename>adt-installer.conf</filename> file:
|
|
|
|
|
|
|
|
|
|
<itemizedlist>
|
|
|
|
|
<listitem><para><filename>YOCTOADT_IPKG_REPO</filename> – This area
|
|
|
|
|
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
|
|
|
|
|
<filename>YOCTOADT_IPKG_REPO</filename>, you need to be sure that the
|
|
|
|
|
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>
|
|
|
|
|
<listitem><para><filename>YOCTOADT-TARGETS</filename> – The machine
|
|
|
|
|
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.
|
2011-03-14 23:47:21 +00:00
|
|
|
|
<note>
|
|
|
|
|
To boot QEMU images using our userspace NFS server, you need
|
|
|
|
|
to be running portmap or rpcbind.
|
|
|
|
|
If you are running rpcbind, you will also need to add the -i
|
|
|
|
|
option when rpcbind starts up.
|
|
|
|
|
Please make sure you understand the security implications of doing this.
|
|
|
|
|
Your firewall settings may also have to be modified to allow
|
|
|
|
|
NFS booting to work.
|
|
|
|
|
</note>
|
2011-06-23 14:24:43 +00:00
|
|
|
|
</para></listitem>
|
|
|
|
|
<listitem><para><filename>YOCTOADT_ROOTFS_<arch></filename> - The root
|
2011-06-23 16:52:34 +00:00
|
|
|
|
filesystem images you want to download from the <filename>YOCTOADT_IPKG_REPO</filename>
|
|
|
|
|
repository.
|
2011-06-23 14:24:43 +00:00
|
|
|
|
</para></listitem>
|
|
|
|
|
<listitem><para><filename>YOCTOADT_TARGET_SYSROOT_IMAGE_<arch></filename> - The
|
2011-06-23 16:52:34 +00:00
|
|
|
|
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 "minimal" or "sato-sdk".
|
2011-06-23 14:24:43 +00:00
|
|
|
|
</para></listitem>
|
|
|
|
|
<listitem><para><filename>YOCTOADT_TARGET_SYSROOT_LOC_<arch></filename> - The
|
2011-06-23 16:52:34 +00:00
|
|
|
|
location on the development host where the target sysroot will be created.
|
2011-06-23 14:24:43 +00:00
|
|
|
|
</para></listitem>
|
|
|
|
|
</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,
|
|
|
|
|
run the installer using the following command:
|
|
|
|
|
<literallayout class='monospaced'>
|
2011-03-14 23:47:21 +00:00
|
|
|
|
$ 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
|
|
|
|
|
<ulink url='http://www.yoctoproject.org/docs/yocto-project-qs/yocto-project-qs.html'>
|
|
|
|
|
Yocto Project Quick Start</ulink> then you will have libtool installed.
|
|
|
|
|
</note>
|
2011-03-14 20:19:44 +00:00
|
|
|
|
|
2011-06-23 14:24:43 +00:00
|
|
|
|
<para>
|
|
|
|
|
Once the installer begins to run you are asked whether you want to run in
|
|
|
|
|
interactive or silent mode.
|
|
|
|
|
If you want to closely monitor the installation then choose “I” for interactive
|
|
|
|
|
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
|
|
|
|
|
<filename>/opt/poky/$SDKVERSION</filename>,
|
|
|
|
|
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>
|
|
|
|
|
|
|
|
|
|
</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>
|
|
|
|
|
<para>
|
|
|
|
|
If you want to simply install the cross-toolchain by hand you can do so by using an existing
|
|
|
|
|
cross-toolchain tarball.
|
2011-06-23 16:52:34 +00:00
|
|
|
|
If you install the cross-toolchain by hand you will have to set up the target 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
|
|
|
|
|
<ulink url='http://autobuilder.yoctoproject.org/downloads/yocto-1.0/toolchain'></ulink>
|
|
|
|
|
and find the folder that matches your host development system
|
|
|
|
|
(i.e. 'i686' for 32-bit machines or 'x86_64' for 64-bit machines).</para>
|
|
|
|
|
</listitem>
|
|
|
|
|
<listitem><para>Go into that folder and download the toolchain tarball 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 arm target go into the
|
|
|
|
|
<filename>x86_64</filename> folder and download the following tarball:
|
|
|
|
|
<literallayout class='monospaced'>
|
|
|
|
|
yocto-eglibc-x86_64-arm-toolchain-gmae-1.0.tar.bz2
|
|
|
|
|
</literallayout>
|
2011-03-14 23:47:21 +00:00
|
|
|
|
<note>
|
2011-06-23 14:24:43 +00:00
|
|
|
|
Alternatively you can build the toolchain tarball if you have a Yocto Project build tree.
|
|
|
|
|
Use the <filename>bitbake meta-toolchain</filename> command after you have
|
|
|
|
|
sourced the <filename>poky-build-init script</filename> located in the Yocto Project
|
|
|
|
|
source directory.
|
|
|
|
|
When the <filename>bitbake</filename> command completes the toolchain tarball will
|
|
|
|
|
be in <filename>tmp/deploy/sdk</filename> in the Yocto Project build tree.
|
|
|
|
|
</note></para></listitem>
|
2011-03-14 23:47:21 +00:00
|
|
|
|
<listitem><para>Make sure you are in the root directory and then expand
|
|
|
|
|
the tarball.
|
2011-06-23 14:24:43 +00:00
|
|
|
|
The tarball expands into <filename>/opt/poky/$SDKVERSION</filename>.
|
|
|
|
|
Once the tarball in unpacked the cross-toolchain is installed.
|
|
|
|
|
You will notice environment setup files for the cross-toolchain in the directory.
|
2011-03-14 23:47:21 +00:00
|
|
|
|
</para></listitem>
|
|
|
|
|
</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-03-14 23:47:21 +00:00
|
|
|
|
<para>
|
2011-07-14 14:00:42 +00:00
|
|
|
|
A final way of installing just the cross-toolchain is to use BitBake within an existing
|
2011-06-23 14:24:43 +00:00
|
|
|
|
Yocto Project build tree.
|
|
|
|
|
Follow these steps:
|
|
|
|
|
<orderedlist>
|
|
|
|
|
<listitem><para>Source the environment setup script located in the Yocto Project
|
|
|
|
|
source directory.
|
|
|
|
|
The script has the string <filename>init-build-env</filename>
|
|
|
|
|
as part of the name.</para></listitem>
|
|
|
|
|
<listitem><para>At this point you should be sure that the
|
|
|
|
|
<filename>MACHINE</filename> variable
|
|
|
|
|
in the <filename>local.conf</filename> file is set for the target architecture.
|
|
|
|
|
You can find the <filename>local.conf</filename> file in the Yocto Project source
|
|
|
|
|
directory.
|
|
|
|
|
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>
|
|
|
|
|
<listitem><para>Run <filename>bitbake meta-ide-support</filename> to complete the
|
|
|
|
|
cross-toolchain installation.
|
|
|
|
|
<note>If you change your working directory after you source the environment
|
2011-07-14 14:00:42 +00:00
|
|
|
|
setup script and before you run the BitBake command the command will not work.
|
|
|
|
|
Be sure to run the BitBake command immediately after checking or editing the
|
2011-06-23 14:24:43 +00:00
|
|
|
|
<filename>local.conf</filename> but without changing your working directory.</note>
|
2011-07-14 14:00:42 +00:00
|
|
|
|
Once BitBake finishes, the cross-toolchain is installed.
|
2011-06-23 14:24:43 +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>
|
|
|
|
|
</orderedlist>
|
2011-03-14 23:47:21 +00:00
|
|
|
|
</para>
|
|
|
|
|
</section>
|
|
|
|
|
</section>
|
|
|
|
|
|
|
|
|
|
<section id='setting-up-the-environment'>
|
|
|
|
|
<title>Setting Up the Environment</title>
|
|
|
|
|
<para>
|
2011-06-23 14:24:43 +00:00
|
|
|
|
Before you can use the cross-toolchain you need to set up the toolchain environment by
|
2011-03-14 23:47:21 +00:00
|
|
|
|
sourcing the 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,
|
2011-03-14 23:47:21 +00:00
|
|
|
|
then you can find this script in the <filename>/opt/poky/$SDKVERSION</filename>
|
|
|
|
|
directory.
|
2011-07-14 14:00:42 +00:00
|
|
|
|
If you used BitBake and the Yocto Project Build Tree to install the cross-toolchain
|
2011-06-23 14:44:29 +00:00
|
|
|
|
then you can find the environment setup scripts in in the Yocto Project build tree
|
|
|
|
|
in the <filename>tmp</filename> directory.
|
2011-03-14 23:47:21 +00:00
|
|
|
|
</para>
|
|
|
|
|
|
|
|
|
|
<para>
|
|
|
|
|
Be sure to run the environment setup script that matches the architecture for
|
|
|
|
|
which you are developing.
|
|
|
|
|
Environment setup scripts begin with the string “environment-setup” and include as
|
|
|
|
|
part of their name the architecture.
|
|
|
|
|
For example, the environment setup script for a 64-bit IA-based architecture would
|
|
|
|
|
be the following:
|
|
|
|
|
<literallayout class='monospaced'>
|
2011-06-23 14:44:29 +00:00
|
|
|
|
/opt/poky/1.0/environment-setup-x86_64-poky-linux
|
2011-03-14 23:47:21 +00:00
|
|
|
|
</literallayout>
|
|
|
|
|
</para>
|
|
|
|
|
</section>
|
|
|
|
|
|
|
|
|
|
<section id='kernels-and-filesystem-images'>
|
|
|
|
|
<title>Kernels and Filesystem Images</title>
|
|
|
|
|
<para>
|
|
|
|
|
You will need to have a kernel and filesystem image to boot using your
|
|
|
|
|
hardware or the QEMU emulator.
|
|
|
|
|
That means you either have to build them or know where to get them.
|
|
|
|
|
You can find lots of details on how to get or build images and kernels for your
|
|
|
|
|
architecture in the "Yocto Project Quick Start" found at
|
|
|
|
|
<ulink url='http://www.yoctoproject.org/docs/yocto-quick-start/yocto-project-qs.html'></ulink>.
|
|
|
|
|
<note>
|
|
|
|
|
Yocto Project provides basic kernels and filesystem images for several
|
2011-06-23 14:47:42 +00:00
|
|
|
|
architectures (x86, x86-64, mips, powerpc, and arm) that you can use
|
2011-03-14 23:47:21 +00:00
|
|
|
|
unaltered in the QEMU emulator.
|
|
|
|
|
These kernels and filesystem images reside in the Yocto Project release
|
2011-06-23 14:47:42 +00:00
|
|
|
|
area - <ulink url='http://autobuilder.yoctoproject.org/downloads/yocto-1.0/machines/'></ulink>
|
2011-03-14 23:47:21 +00:00
|
|
|
|
and are ideal for experimentation within Yocto Project.
|
|
|
|
|
</note>
|
|
|
|
|
</para>
|
|
|
|
|
</section>
|
2011-03-14 20:19:44 +00:00
|
|
|
|
|
|
|
|
|
</chapter>
|
|
|
|
|
<!--
|
|
|
|
|
vim: expandtab tw=80 ts=4
|
|
|
|
|
-->
|