summaryrefslogtreecommitdiff
path: root/documentation/yocto-project-qs
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-01-20 13:59:44 -0800
committerSaul Wold <sgw@linux.intel.com>2011-01-25 11:58:51 -0800
commit63e6319bd18146b5bc25d9b8ab57b294a020cf9a (patch)
tree206d5211f8ecc73fafc622a7a15a50bbf66a02e3 /documentation/yocto-project-qs
parentbcce31b4952a9cdb553d0d593b8539fe721acff6 (diff)
downloadopenembedded-core-63e6319bd18146b5bc25d9b8ab57b294a020cf9a.tar.gz
openembedded-core-63e6319bd18146b5bc25d9b8ab57b294a020cf9a.tar.bz2
openembedded-core-63e6319bd18146b5bc25d9b8ab57b294a020cf9a.zip
documentation/yocto-project-qs/yocto-project-qs.xml: Updated <arch> value for environment setup command
The value for the 64-bit architecture was "x86-64" and not "x86_64". Changed it to be correct. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Diffstat (limited to 'documentation/yocto-project-qs')
-rw-r--r--documentation/yocto-project-qs/yocto-project-qs.xml46
1 files changed, 23 insertions, 23 deletions
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml
index 7223e0a7b7..f62eac16d7 100644
--- a/documentation/yocto-project-qs/yocto-project-qs.xml
+++ b/documentation/yocto-project-qs/yocto-project-qs.xml
@@ -308,8 +308,7 @@
<itemizedlist>
<listitem>
<para>
- Install the stand-alone Yocto toolchain tarball and then set up the
- environment to emulate the hardware.
+ Install the stand-alone Yocto toolchain tarball.
</para>
</listitem>
<listitem>
@@ -326,14 +325,14 @@
</listitem>
<listitem>
<para>
- Start the QEMU emulator.
+ Set up the environment to emulate the hardware and then start the QEMU emulator.
</para>
</listitem>
</itemizedlist>
- <section id='installing-the-toolchain-and-setting-up-the-environment'>
- <title>Installing the Toolchain and Setting Up the Environment</title>
+ <section id='installing-the-toolchain'>
+ <title>Installing the Toolchain</title>
<para>
You can download the pre-built toolchain, which includes the poky-qemu script and
support files, from <ulink url='http://yoctoproject.org/downloads/yocto-0.9/toolchain/'></ulink>.
@@ -379,21 +378,6 @@
$ sudo tar -xvjf yocto-eglibc-x86_64-i586-toolchain-sdk-0.9.tar.bz2
</literallayout>
</para>
-
- <para>
- The following command form sets up the emulation environment.
- </para>
-
- <literallayout class='monospaced'>
- $ source /opt/poky/environment-setup-&lt;<emphasis>arch</emphasis>&gt;-poky-linux-&lt;<emphasis>if</emphasis>&gt;
-
- Where:
- &lt;<emphasis>arch</emphasis>&gt; is a string representing the target architecture:
- i586, x86-64, ppc603e, mips, or armv5te.
-
- &lt;<emphasis>if</emphasis>&gt; is a string representing an embedded application binary interface.
- Not all setup scripts include this string.
- </literallayout>
</section>
<section id='downloading-the-pre-built-linux-kernel'>
@@ -441,8 +425,24 @@
</literallayout>
</section>
- <section id='starting-the-qemu-emulator'>
- <title>Starting the QEMU Emulator</title>
+ <section id='setting-up-the-environment-and-starting-the-qemu-emulator'>
+ <title>Setting Up the Environment and Starting the QEMU Emulator</title>
+ <para>
+ Before you start the QEMU emulator you need to set up the emulation environment.
+ The following command form sets up the emulation environment.
+ </para>
+
+ <literallayout class='monospaced'>
+ $ source /opt/poky/environment-setup-&lt;<emphasis>arch</emphasis>&gt;-poky-linux-&lt;<emphasis>if</emphasis>&gt;
+
+ Where:
+ &lt;<emphasis>arch</emphasis>&gt; is a string representing the target architecture:
+ i586, x86_64, ppc603e, mips, or armv5te.
+
+ &lt;<emphasis>if</emphasis>&gt; is a string representing an embedded application binary interface.
+ Not all setup scripts include this string.
+ </literallayout>
+
<para>
Finally, this command form invokes the QEMU emulator
</para>
@@ -463,7 +463,7 @@
<para>
Continuing with the example, the following two commands setup the emulation
- environment and launch QEMu.
+ environment and launch QEMU.
The kernel and filesystem are for a 32-bit target architecture.
</para>