summaryrefslogtreecommitdiffstats
path: root/documentation/adt-manual/adt-prepare.xml
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/adt-prepare.xml
parenta8b0bc49803ef96740d1f2f90b0dca1302d806d5 (diff)
downloadpoky-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/adt-prepare.xml')
-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 3d902e4e5f..b4e27baf6f 100644
--- a/documentation/adt-manual/adt-prepare.xml
+++ b/documentation/adt-manual/adt-prepare.xml
@@ -516,31 +516,62 @@
516 <title>Extracting the Root Filesystem</title> 516 <title>Extracting the Root Filesystem</title>
517 517
518 <para> 518 <para>
519 You must extract the root filesystem if you want to boot the image using NFS 519 If you install your toolchain by hand or build it using BitBake and
520 or you want to use the root filesystem as the target sysroot. 520 you need a root filesystem, you need to extract it separately.
521 For example, the Eclipse IDE environment with the Eclipse Yocto Plug-in installed allows you 521 If you use the ADT Installer to install the ADT, the root
522 to use QEMU to boot under NFS. 522 filesystem is automatically extracted and installed.
523 Another example is if you want to develop your target application using the 523 </para>
524 root filesystem as the target sysroot. 524
525 <para>
526 Here are some cases where you need to extract the root filesystem:
527 <itemizedlist>
528 <listitem><para>You want to boot the image using NFS.
529 </para></listitem>
530 <listitem><para>You want to use the root filesystem as the
531 target sysroot.
532 For example, the Eclipse IDE environment with the Eclipse
533 Yocto Plug-in installed allows you to use QEMU to boot
534 under NFS.</para></listitem>
535 <listitem><para>You want to develop your target application
536 using the root filesystem as the target sysroot.
537 </para></listitem>
538 </itemizedlist>
525 </para> 539 </para>
526 540
527 <para> 541 <para>
528 To extract the root filesystem, first <filename>source</filename> 542 To extract the root filesystem, first <filename>source</filename>
529 the cross-development environment setup script and then 543 the cross-development environment setup script.
530 use the <filename>runqemu-extract-sdk</filename> command on the 544 If you built the toolchain in the Build Directory, you will find
545 the toolchain environment script in the
546 <filename>tmp</filename> directory.
547 If you installed the toolchain by hand, the environment setup
548 script is located in <filename>opt/poky/&DISTRO;</filename>.
549 </para>
550
551 <para>
552 After sourcing the environment script, use the
553 <filename>runqemu-extract-sdk</filename> command and provide the
531 filesystem image. 554 filesystem image.
532 For example, the following commands set up the environment and then extract 555 </para>
533 the root filesystem from a previously built filesystem image tarball named 556
534 <filename>core-image-sato-sdk-qemux86-2011091411831.rootfs.tar.bz2</filename>. 557 <para>
535 The example extracts the root filesystem into the <filename>$HOME/qemux86-sato</filename> 558 Following is an example.
536 directory: 559 The second command sets up the environment.
560 In this case, the setup script is located in the
561 <filename>/opt/poky/&DISTRO;</filename> directory.
562 The third command extracts the root filesystem from a previously
563 built filesystem that is located in the
564 <filename>~/Downloads</filename> directory.
565 Furthermore, this command extracts the root filesystem into the
566 <filename>$HOME/qemux86-sato</filename> directory:
537 <literallayout class='monospaced'> 567 <literallayout class='monospaced'>
538 $ source $HOME/toolchain_dir/environment-setup-i586-poky-linux 568 $ cd ~
569 $ source /opt/poky/&DISTRO;/environment-setup-i586-poky-linux
539 $ runqemu-extract-sdk \ 570 $ runqemu-extract-sdk \
540 ~Downloads/core-image-sato-sdk-qemux86-2011091411831.rootfs.tar.bz2 \ 571 ~Downloads/core-image-sato-sdk-qemux86-2011091411831.rootfs.tar.bz2 \
541 $HOME/qemux86-sato 572 $HOME/qemux86-sato
542 </literallayout> 573 </literallayout>
543 In this case, you could now point to the target sysroot at 574 You could now point to the target sysroot at
544 <filename>$HOME/qemux86-sato</filename>. 575 <filename>$HOME/qemux86-sato</filename>.
545 </para> 576 </para>
546 </section> 577 </section>