diff options
| -rw-r--r-- | documentation/adt-manual/adt-eclipse.xml | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/documentation/adt-manual/adt-eclipse.xml b/documentation/adt-manual/adt-eclipse.xml index d3601d4e11..1e6493e660 100644 --- a/documentation/adt-manual/adt-eclipse.xml +++ b/documentation/adt-manual/adt-eclipse.xml | |||
| @@ -147,24 +147,24 @@ | |||
| 147 | <section id='configuring-the-cross-compiler-options'> | 147 | <section id='configuring-the-cross-compiler-options'> |
| 148 | <title>Configuring the Cross-Compiler Options</title> | 148 | <title>Configuring the Cross-Compiler Options</title> |
| 149 | <para> | 149 | <para> |
| 150 | Choose between ‘SDK Root Mode’ and ‘Poky Tree Mode’ for Cross | 150 | Choose between ‘Stand-alone Prebuilt Toolchain’ and ‘Build System Derived Toolchain’ for Cross |
| 151 | Compiler Options. | 151 | Compiler Options. |
| 152 | <itemizedlist> | 152 | <itemizedlist> |
| 153 | <listitem><para><emphasis>SDK Root Mode</emphasis> – Select this mode | 153 | <listitem><para><emphasis>Stand-alone Prebuilt Toolchain</emphasis> – Select this mode |
| 154 | when you are not concerned with building a target image or you do not have | 154 | when you are not concerned with building a target image or you do not have |
| 155 | a Yocto Project build tree on your development system. | 155 | a Yocto Project build tree on your development system. |
| 156 | For example, suppose you are an application developer and do not | 156 | For example, suppose you are an application developer and do not |
| 157 | need to build a target image. | 157 | need to build a target image. |
| 158 | Instead, you just want to use an architecture-specific toolchain on an | 158 | Instead, you just want to use an architecture-specific toolchain on an |
| 159 | existing kernel and target root filesystem. | 159 | existing kernel and target root filesystem. |
| 160 | When you use SDK Root Mode you are using the toolchain installed | 160 | When you use Stand-alone Prebuilt Toolchain you are using the toolchain installed |
| 161 | in the <filename>/opt/poky</filename> directory.</para></listitem> | 161 | in the <filename>/opt/poky</filename> directory.</para></listitem> |
| 162 | <listitem><para><emphasis>Poky Tree Mode</emphasis> – Select this mode | 162 | <listitem><para><emphasis>Build System Derived Toolchain</emphasis> – Select this mode |
| 163 | if you are building images for target hardware or your | 163 | if you are building images for target hardware or your |
| 164 | development environment already has a Yocto Project build tree. | 164 | development environment already has a Yocto Project build tree. |
| 165 | In this case you likely already have a Yocto Project build tree installed on | 165 | In this case you likely already have a Yocto Project build tree installed on |
| 166 | your system or you (or someone else) will be building one. | 166 | your system or you (or someone else) will be building one. |
| 167 | When you use the Poky Tree Mode you are using the toolchain bundled | 167 | When you use the Build System Derived Toolchain you are using the toolchain bundled |
| 168 | inside the Yocto Project build tree. | 168 | inside the Yocto Project build tree. |
| 169 | If you use this mode you must also supply the Yocto Project build directory | 169 | If you use this mode you must also supply the Yocto Project build directory |
| 170 | in the Preferences Dialog.</para></listitem> | 170 | in the Preferences Dialog.</para></listitem> |
| @@ -179,7 +179,7 @@ | |||
| 179 | target hardware is created on the development system by the ADT Installer. | 179 | target hardware is created on the development system by the ADT Installer. |
| 180 | The QEMU user-space tools, the | 180 | The QEMU user-space tools, the |
| 181 | NFS boot process and the cross-toolchain all use the sysroot location | 181 | NFS boot process and the cross-toolchain all use the sysroot location |
| 182 | regardless of the mode you select (SDK Root Mode or Poky Tree Mode). | 182 | regardless of the mode you select (Stand-alone Prebuilt Toolchain or Build System Derived Toolchain). |
| 183 | </para> | 183 | </para> |
| 184 | </section> | 184 | </section> |
| 185 | 185 | ||
| @@ -213,9 +213,9 @@ | |||
| 213 | you will be using the QEMU emulator. | 213 | you will be using the QEMU emulator. |
| 214 | If you are using the emulator you also need to locate the Kernel | 214 | If you are using the emulator you also need to locate the Kernel |
| 215 | and specify any custom options.</para> | 215 | and specify any custom options.</para> |
| 216 | <para>In Poky Tree Mode the targe kernel you built will be located in the | 216 | <para>In Build System Derived Toolchain the targe kernel you built will be located in the |
| 217 | Yocto Project build tree in <filename>tmp/deploy/images</filename> directory. | 217 | Yocto Project build tree in <filename>tmp/deploy/images</filename> directory. |
| 218 | In SDK Root Mode the pre-built kernel you downloaded is located | 218 | In Stand-alone Prebuilt Toolchain the pre-built kernel you downloaded is located |
| 219 | in the directory you specified when you downloaded the image.</para> | 219 | in the directory you specified when you downloaded the image.</para> |
| 220 | <para>Most custom options are for advanced QEMU users to further | 220 | <para>Most custom options are for advanced QEMU users to further |
| 221 | customize their QEMU instance. | 221 | customize their QEMU instance. |
| @@ -290,7 +290,7 @@ | |||
| 290 | This brings up the project Yocto Settings Dialog. | 290 | This brings up the project Yocto Settings Dialog. |
| 291 | Settings are inherited from the default project configuration. | 291 | Settings are inherited from the default project configuration. |
| 292 | The information in this dialogue is identical to that chosen earlier | 292 | The information in this dialogue is identical to that chosen earlier |
| 293 | for the Cross Compiler Option (SDK Root Mode or Poky Tree Mode), | 293 | for the Cross Compiler Option (Stand-alone Prebuilt Toolchain or Build System Derived Toolchain), |
| 294 | the Target Architecture, and the Target Options. | 294 | the Target Architecture, and the Target Options. |
| 295 | The settings are inherited from the Yocto Plug-in configuration performed | 295 | The settings are inherited from the Yocto Plug-in configuration performed |
| 296 | after installing the plug-in.</para></listitem> | 296 | after installing the plug-in.</para></listitem> |
