summaryrefslogtreecommitdiffstats
path: root/documentation/adt-manual
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-10-25 09:43:43 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-11-01 17:09:53 +0000
commit853df59bf991aa9dc15b25732291fdc9a01b5c99 (patch)
tree8269fff6b6fa177d2e3263a4bd07bc5c31d92571 /documentation/adt-manual
parenta8b0bc49803ef96740d1f2f90b0dca1302d806d5 (diff)
downloadast2050-yocto-poky-853df59bf991aa9dc15b25732291fdc9a01b5c99.zip
ast2050-yocto-poky-853df59bf991aa9dc15b25732291fdc9a01b5c99.tar.gz
adt-manual: Edits to "Extracting the Root Filesystem" section
This section was a bit confusing. I added some lists to make it clearer when this step is necessary. I also added some more detail on where to find the setup script. (From yocto-docs rev: 0518aeeb0b395c84233bace26fc3f40234e044b3) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/adt-manual')
-rw-r--r--documentation/adt-manual/adt-prepare.xml61
1 files changed, 46 insertions, 15 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml
index 3d902e4..b4e27ba 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -516,31 +516,62 @@
<title>Extracting the Root Filesystem</title>
<para>
- 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.
- For example, the Eclipse IDE environment with the Eclipse Yocto Plug-in installed allows you
- to use QEMU to boot under NFS.
- Another example is if you want to develop your target application using the
- root filesystem as the target sysroot.
+ If you install your toolchain by hand or build it using BitBake and
+ you need a root filesystem, you need to extract it separately.
+ If you use the ADT Installer to install the ADT, the root
+ filesystem is automatically extracted and installed.
+ </para>
+
+ <para>
+ Here are some cases where you need to extract the root filesystem:
+ <itemizedlist>
+ <listitem><para>You want to boot the image using NFS.
+ </para></listitem>
+ <listitem><para>You want to use the root filesystem as the
+ target sysroot.
+ For example, the Eclipse IDE environment with the Eclipse
+ Yocto Plug-in installed allows you to use QEMU to boot
+ under NFS.</para></listitem>
+ <listitem><para>You want to develop your target application
+ using the root filesystem as the target sysroot.
+ </para></listitem>
+ </itemizedlist>
</para>
<para>
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
+ the cross-development environment setup script.
+ If you built the toolchain in the Build Directory, you will find
+ the toolchain environment script in the
+ <filename>tmp</filename> directory.
+ If you installed the toolchain by hand, the environment setup
+ script is located in <filename>opt/poky/&DISTRO;</filename>.
+ </para>
+
+ <para>
+ After sourcing the environment script, use the
+ <filename>runqemu-extract-sdk</filename> command and provide the
filesystem image.
- For example, the following commands set up the environment and then extract
- the root filesystem from a previously built filesystem image tarball named
- <filename>core-image-sato-sdk-qemux86-2011091411831.rootfs.tar.bz2</filename>.
- The example extracts the root filesystem into the <filename>$HOME/qemux86-sato</filename>
- directory:
+ </para>
+
+ <para>
+ Following is an example.
+ The second command sets up the environment.
+ In this case, the setup script is located in the
+ <filename>/opt/poky/&DISTRO;</filename> directory.
+ The third command extracts the root filesystem from a previously
+ built filesystem that is located in the
+ <filename>~/Downloads</filename> directory.
+ Furthermore, this command extracts the root filesystem into the
+ <filename>$HOME/qemux86-sato</filename> directory:
<literallayout class='monospaced'>
- $ source $HOME/toolchain_dir/environment-setup-i586-poky-linux
+ $ cd ~
+ $ source /opt/poky/&DISTRO;/environment-setup-i586-poky-linux
$ runqemu-extract-sdk \
~Downloads/core-image-sato-sdk-qemux86-2011091411831.rootfs.tar.bz2 \
$HOME/qemux86-sato
</literallayout>
- In this case, you could now point to the target sysroot at
+ You could now point to the target sysroot at
<filename>$HOME/qemux86-sato</filename>.
</para>
</section>
OpenPOWER on IntegriCloud