sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

documentation/adt-manual/adt-eclipse.xml: Updated new modes for tree 

The "Poky Tree Mode" has been replaced with "Build System Derived
Toolchain".  SDK Root Mode has been replaced with Stand-alone
Prebuilt Toolchain.

(From yocto-docs rev: 453f7c030e6d7625d382563e2f2ec569f76e95eb)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2011-06-23 13:07:56 -07:00 committed by Richard Purdie
parent bba2e72ace
commit 7adc615a39
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
documentation/adt-manual/adt-eclipse.xml
View File

@ -147,24 +147,24 @@
<section id='configuring-the-cross-compiler-options'>
<title>Configuring the Cross-Compiler Options</title>
<para>
Choose between ‘SDK Root Mode’ and ‘Poky Tree Mode’ for Cross
Choose between ‘Stand-alone Prebuilt Toolchain’ and ‘Build System Derived Toolchain’ for Cross
Compiler Options.
<itemizedlist>
<listitem><para><emphasis>SDK Root Mode</emphasis> – Select this mode
<listitem><para><emphasis>Stand-alone Prebuilt Toolchain</emphasis> – Select this mode
when you are not concerned with building a target image or you do not have
a Yocto Project build tree on your development system.
For example, suppose you are an application developer and do not
need to build a target image.
Instead, you just want to use an architecture-specific toolchain on an
existing kernel and target root filesystem.
When you use SDK Root Mode you are using the toolchain installed
When you use Stand-alone Prebuilt Toolchain you are using the toolchain installed
in the <filename>/opt/poky</filename> directory.</para></listitem>
<listitem><para><emphasis>Poky Tree Mode</emphasis> – Select this mode
<listitem><para><emphasis>Build System Derived Toolchain</emphasis> – Select this mode
if you are building images for target hardware or your
development environment already has a Yocto Project build tree.
In this case you likely already have a Yocto Project build tree installed on
your system or you (or someone else) will be building one.
When you use the Poky Tree Mode you are using the toolchain bundled
When you use the Build System Derived Toolchain you are using the toolchain bundled
inside the Yocto Project build tree.
If you use this mode you must also supply the Yocto Project build directory
in the Preferences Dialog.</para></listitem>
@ -179,7 +179,7 @@
target hardware is created on the development system by the ADT Installer.
The QEMU user-space tools, the
NFS boot process and the cross-toolchain all use the sysroot location
regardless of the mode you select (SDK Root Mode or Poky Tree Mode).
regardless of the mode you select (Stand-alone Prebuilt Toolchain or Build System Derived Toolchain).
</para>
</section>
@ -213,9 +213,9 @@
you will be using the QEMU emulator.
If you are using the emulator you also need to locate the Kernel
and specify any custom options.</para>
<para>In Poky Tree Mode the targe kernel you built will be located in the
<para>In Build System Derived Toolchain the targe kernel you built will be located in the
Yocto Project build tree in <filename>tmp/deploy/images</filename> directory.
In SDK Root Mode the pre-built kernel you downloaded is located
In Stand-alone Prebuilt Toolchain the pre-built kernel you downloaded is located
in the directory you specified when you downloaded the image.</para>
<para>Most custom options are for advanced QEMU users to further
customize their QEMU instance.
@ -290,7 +290,7 @@
This brings up the project Yocto Settings Dialog.
Settings are inherited from the default project configuration.
The information in this dialogue is identical to that chosen earlier
for the Cross Compiler Option (SDK Root Mode or Poky Tree Mode),
for the Cross Compiler Option (Stand-alone Prebuilt Toolchain or Build System Derived Toolchain),
the Target Architecture, and the Target Options.
The settings are inherited from the Yocto Plug-in configuration performed
after installing the plug-in.</para></listitem>