summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--documentation/adt-manual/adt-eclipse.xml25
1 files changed, 12 insertions, 13 deletions
diff --git a/documentation/adt-manual/adt-eclipse.xml b/documentation/adt-manual/adt-eclipse.xml
index 759ce8f5e4..324d6dbcd7 100644
--- a/documentation/adt-manual/adt-eclipse.xml
+++ b/documentation/adt-manual/adt-eclipse.xml
@@ -225,10 +225,10 @@
225 If you are using a stand-alone pre-built toolchain, you should be pointing to the 225 If you are using a stand-alone pre-built toolchain, you should be pointing to the
226 <filename>/opt/poky/$SDKVERSION</filename> directory. 226 <filename>/opt/poky/$SDKVERSION</filename> directory.
227 This is the location for toolchains installed by the ADT Installer or by hand. 227 This is the location for toolchains installed by the ADT Installer or by hand.
228 Sections <link linkend='configuring-and-running-the-adt-installer-script'> 228 Sections "<link linkend='configuring-and-running-the-adt-installer-script'>Configuring
229 Configuring and Running the ADT Installer Script</link> and 229 and Running the ADT Installer Script</link>" and
230 <link linkend='using-an-existing-toolchain-tarball'> 230 "<link linkend='using-an-existing-toolchain-tarball'>Using a Cross-Toolchain
231 Using a Cross-Toolchain Tarball</link> describe two ways to install 231 Tarball</link>" describe two ways to install
232 a stand-alone cross-toolchain in the 232 a stand-alone cross-toolchain in the
233 <filename>/opt/poky</filename> directory. 233 <filename>/opt/poky</filename> directory.
234 <note>It is possible to install a stand-alone cross-toolchain in a directory 234 <note>It is possible to install a stand-alone cross-toolchain in a directory
@@ -237,8 +237,8 @@
237 <para>If you are using a system-derived toolchain, the path you provide 237 <para>If you are using a system-derived toolchain, the path you provide
238 for the <filename>Toolchain Root Location</filename> 238 for the <filename>Toolchain Root Location</filename>
239 field is the Yocto Project's build directory. 239 field is the Yocto Project's build directory.
240 See section <link linkend='using-the-toolchain-from-within-the-build-tree'> 240 See section "<link linkend='using-the-toolchain-from-within-the-build-tree'>Using
241 Using BitBake and the Yocto Project Build Tree</link> for 241 BitBake and the Yocto Project Build Tree</link>" for
242 information on how to install the toolchain into the Yocto 242 information on how to install the toolchain into the Yocto
243 Project build tree.</para></listitem> 243 Project build tree.</para></listitem>
244 <listitem><para><emphasis>Specify the Sysroot Location:</emphasis> 244 <listitem><para><emphasis>Specify the Sysroot Location:</emphasis>
@@ -255,8 +255,7 @@
255 The pull-down menu should have the supported architectures. 255 The pull-down menu should have the supported architectures.
256 If the architecture you need is not listed in the menu, you 256 If the architecture you need is not listed in the menu, you
257 will need to build the image. 257 will need to build the image.
258 See the 258 See the "<ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#building-image'>Building an Image</ulink>" section of the
259 <ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#building-image'> Building an Image</ulink> section of the
260 <ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html'> 259 <ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html'>
261 The Yocto Project Quick Start</ulink> for more information.</para></listitem> 260 The Yocto Project Quick Start</ulink> for more information.</para></listitem>
262 </itemizedlist> 261 </itemizedlist>
@@ -317,7 +316,7 @@
317 This section describes how to create Autotools-based projects from within 316 This section describes how to create Autotools-based projects from within
318 the Eclipse IDE. 317 the Eclipse IDE.
319 For information on creating Makefile-based projects in a terminal window, see the section 318 For information on creating Makefile-based projects in a terminal window, see the section
320 <link linkend='using-the-command-line'>Using the Command Line</link>. 319 "<link linkend='using-the-command-line'>Using the Command Line</link>".
321 </para> 320 </para>
322 321
323 <para> 322 <para>
@@ -350,8 +349,8 @@
350<title>Configuring the Cross-Toolchains</title> 349<title>Configuring the Cross-Toolchains</title>
351 350
352 <para> 351 <para>
353 The previous section, <link linkend='configuring-the-eclipse-yocto-plug-in'> 352 The previous section, "<link linkend='configuring-the-eclipse-yocto-plug-in'>Configuring
354 Configuring the Eclipse Yocto Plug-in</link>, sets up the default project 353 the Eclipse Yocto Plug-in</link>", sets up the default project
355 configurations. 354 configurations.
356 You can change these settings for a given project by following these steps: 355 You can change these settings for a given project by following these steps:
357 <orderedlist> 356 <orderedlist>
@@ -363,8 +362,8 @@
363 <para>Yocto ADT Settings are inherited from the default project configuration. 362 <para>Yocto ADT Settings are inherited from the default project configuration.
364 The information in this dialog is identical to that chosen earlier 363 The information in this dialog is identical to that chosen earlier
365 for the Cross Compiler Options and Target Options as described in the 364 for the Cross Compiler Options and Target Options as described in the
366 <link linkend='configuring-the-eclipse-yocto-plug-in'> 365 "<link linkend='configuring-the-eclipse-yocto-plug-in'>Configuring the Eclipse
367 Configuring the Eclipse Yocto Plug-in</link> section.</para></listitem> 366 Yocto Plug-in</link>" section.</para></listitem>
368 <listitem><para>Select <filename>Project -&gt; Reconfigure Project</filename>: 367 <listitem><para>Select <filename>Project -&gt; Reconfigure Project</filename>:
369 This selection reconfigures the project by running 368 This selection reconfigures the project by running
370 <filename>autogen.sh</filename> in the workspace for your project. 369 <filename>autogen.sh</filename> in the workspace for your project.