summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
Diffstat
-rw-r--r--documentation/sdk-manual/sdk-appendix-neon.xml48
-rw-r--r--documentation/sdk-manual/sdk-eclipse-project.xml43
2 files changed, 43 insertions, 48 deletions
diff --git a/documentation/sdk-manual/sdk-appendix-neon.xml b/documentation/sdk-manual/sdk-appendix-neon.xml
index 7312bb9ba0..1a6fbcfed6 100644
--- a/documentation/sdk-manual/sdk-appendix-neon.xml
+++ b/documentation/sdk-manual/sdk-appendix-neon.xml
@@ -381,15 +381,15 @@
381 the sysroot location, and select the target 381 the sysroot location, and select the target
382 architecture. 382 architecture.
383 <itemizedlist> 383 <itemizedlist>
384 <listitem><para><emphasis>Selecting the Toolchain Type:</emphasis> 384 <listitem><para>
385 Choose between 385 <emphasis>Selecting the Toolchain Type:</emphasis>
386 <filename>Standalone pre-built toolchain</filename> 386 Choose between "Standalone pre-built toolchain"
387 and 387 and
388 <filename>Build system derived toolchain</filename> 388 "Build system derived toolchain" for Cross Compiler
389 for Cross Compiler Options. 389 Options.
390 <itemizedlist> 390 <itemizedlist>
391 <listitem><para><emphasis> 391 <listitem><para>
392 <filename>Standalone Pre-built Toolchain:</filename></emphasis> 392 <emphasis>Standalone Pre-built Toolchain:</emphasis>
393 Select this type when you are using 393 Select this type when you are using
394 a stand-alone cross-toolchain. 394 a stand-alone cross-toolchain.
395 For example, suppose you are an 395 For example, suppose you are an
@@ -403,24 +403,25 @@
403 and installed a pre-built toolchain 403 and installed a pre-built toolchain
404 for an existing image. 404 for an existing image.
405 </para></listitem> 405 </para></listitem>
406 <listitem><para><emphasis> 406 <listitem><para>
407 <filename>Build System Derived Toolchain:</filename></emphasis> 407 <emphasis>Build System Derived Toolchain:</emphasis>
408 Select this type if you built the 408 Select this type if you built the
409 toolchain as part of the 409 toolchain as part of the
410 <ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink>. 410 <ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink>.
411 When you select 411 When you select "Build system derived
412 <filename>Build system derived toolchain</filename>, 412 toolchain", you are using the toolchain
413 you are using the toolchain built and 413 built and bundled inside the Build
414 bundled inside the Build Directory. 414 Directory.
415 For example, suppose you created a 415 For example, suppose you created a
416 suitable image using the steps in the 416 suitable image using the steps in the
417 <ulink url='https://wiki.yoctoproject.org/wiki/TipsAndTricks/RunningEclipseAgainstBuiltImage'>wiki</ulink>. 417 <ulink url='https://wiki.yoctoproject.org/wiki/TipsAndTricks/RunningEclipseAgainstBuiltImage'>wiki</ulink>.
418 In this situation, you would select the 418 In this situation, you would select
419 <filename>Build system derived toolchain</filename>. 419 "Build system derived toolchain".
420 </para></listitem> 420 </para></listitem>
421 </itemizedlist> 421 </itemizedlist>
422 </para></listitem> 422 </para></listitem>
423 <listitem><para><emphasis>Specify the Toolchain Root Location:</emphasis> 423 <listitem><para>
424 <emphasis>Specify the Toolchain Root Location:</emphasis>
424 If you are using a stand-alone pre-built 425 If you are using a stand-alone pre-built
425 toolchain, you should be pointing to where it is 426 toolchain, you should be pointing to where it is
426 installed (e.g. 427 installed (e.g.
@@ -429,10 +430,10 @@
429 "<link linkend='sdk-installing-the-sdk'>Installing the SDK</link>" 430 "<link linkend='sdk-installing-the-sdk'>Installing the SDK</link>"
430 section for information about how the SDK is 431 section for information about how the SDK is
431 installed.</para> 432 installed.</para>
433
432 <para>If you are using a build system derived 434 <para>If you are using a build system derived
433 toolchain, the path you provide for the 435 toolchain, the path you provide for the
434 <filename>Toolchain Root Location</filename> 436 "Toolchain Root Location" field is the
435 field is the
436 <ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink> 437 <ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink>
437 from which you run the 438 from which you run the
438 <filename>bitbake</filename> command (e.g 439 <filename>bitbake</filename> command (e.g
@@ -441,10 +442,12 @@
441 "<link linkend='sdk-building-an-sdk-installer'>Building an SDK Installer</link>" 442 "<link linkend='sdk-building-an-sdk-installer'>Building an SDK Installer</link>"
442 section. 443 section.
443 </para></listitem> 444 </para></listitem>
444 <listitem><para><emphasis>Specify Sysroot Location:</emphasis> 445 <listitem><para>
446 <emphasis>Specify Sysroot Location:</emphasis>
445 This location is where the root filesystem for 447 This location is where the root filesystem for
446 the target hardware resides. 448 the target hardware resides.
447 </para> 449 </para>
450
448 <para>This location depends on where you 451 <para>This location depends on where you
449 separately extracted and installed the 452 separately extracted and installed the
450 target filesystem when you either built 453 target filesystem when you either built
@@ -465,17 +468,18 @@
465 and you would browse to and select that directory 468 and you would browse to and select that directory
466 (e.g. <filename>/home/scottrif/build/MY_QEMU_ROOTFS</filename>). 469 (e.g. <filename>/home/scottrif/build/MY_QEMU_ROOTFS</filename>).
467 </para> 470 </para>
471
468 <para>For more information on how to install the 472 <para>For more information on how to install the
469 toolchain and on how to extract and install the 473 toolchain and on how to extract and install the
470 sysroot filesystem, see the 474 sysroot filesystem, see the
471 "<link linkend='sdk-building-an-sdk-installer'>Building an SDK Installer</link>" 475 "<link linkend='sdk-building-an-sdk-installer'>Building an SDK Installer</link>"
472 section. 476 section.
473 </para></listitem> 477 </para></listitem>
474 <listitem><para><emphasis>Select the Target Architecture:</emphasis> 478 <listitem><para>
479 <emphasis>Select the Target Architecture:</emphasis>
475 The target architecture is the type of hardware 480 The target architecture is the type of hardware
476 you are going to use or emulate. 481 you are going to use or emulate.
477 Use the pull-down 482 Use the pull-down "Target Architecture" menu
478 <filename>Target Architecture</filename> menu
479 to make your selection. 483 to make your selection.
480 The pull-down menu should have the supported 484 The pull-down menu should have the supported
481 architectures. 485 architectures.
diff --git a/documentation/sdk-manual/sdk-eclipse-project.xml b/documentation/sdk-manual/sdk-eclipse-project.xml
index 56ba4657fb..8f615f754b 100644
--- a/documentation/sdk-manual/sdk-eclipse-project.xml
+++ b/documentation/sdk-manual/sdk-eclipse-project.xml
@@ -647,15 +647,12 @@
647 <listitem><para> 647 <listitem><para>
648 <emphasis>Selecting the Toolchain 648 <emphasis>Selecting the Toolchain
649 Type:</emphasis> 649 Type:</emphasis>
650 Choose between 650 Choose between "Standalone pre-built toolchain"
651 <filename>Standalone pre-built toolchain</filename> 651 and "Build system derived toolchain" for
652 and 652 Cross Compiler Options.
653 <filename>Build system derived toolchain</filename>
654 for Cross Compiler Options.
655 <itemizedlist> 653 <itemizedlist>
656 <listitem><para> 654 <listitem><para>
657 <emphasis> 655 <emphasis>Standalone Pre-built Toolchain:
658 <filename>Standalone Pre-built Toolchain:</filename>
659 </emphasis> 656 </emphasis>
660 Select this type when you are using 657 Select this type when you are using
661 a stand-alone cross-toolchain. 658 a stand-alone cross-toolchain.
@@ -671,29 +668,25 @@
671 for an existing image. 668 for an existing image.
672 </para></listitem> 669 </para></listitem>
673 <listitem><para> 670 <listitem><para>
674 <emphasis> 671 <emphasis>Build System Derived Toolchain:
675 <filename>Build System Derived Toolchain:</filename>
676 </emphasis> 672 </emphasis>
677 Select this type if you built the 673 Select this type if you built the
678 toolchain as part of the 674 toolchain as part of the
679 <ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink>. 675 <ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink>.
680 When you select 676 When you select "Build system derived
681 <filename>Build system derived toolchain</filename>, 677 toolchain", you are using the toolchain
682 you are using the toolchain built 678 built and bundled inside the Build
683 and bundled inside the Build
684 Directory. 679 Directory.
685 For example, suppose you created a 680 For example, suppose you created a
686 suitable image using the steps in the 681 suitable image using the steps in the
687 <ulink url='https://wiki.yoctoproject.org/wiki/TipsAndTricks/RunningEclipseAgainstBuiltImage'>wiki</ulink>. 682 <ulink url='https://wiki.yoctoproject.org/wiki/TipsAndTricks/RunningEclipseAgainstBuiltImage'>wiki</ulink>.
688 In this situation, you would select 683 In this situation, you would select
689 the 684 "Build system derived toolchain".
690 <filename>Build system derived toolchain</filename>.
691 </para></listitem> 685 </para></listitem>
692 </itemizedlist> 686 </itemizedlist>
693 </para></listitem> 687 </para></listitem>
694 <listitem><para> 688 <listitem><para>
695 <emphasis>Specify the Toolchain Root 689 <emphasis>Specify the Toolchain Root Location:</emphasis>
696 Location:</emphasis>
697 If you are using a stand-alone pre-built 690 If you are using a stand-alone pre-built
698 toolchain, you should be pointing to where 691 toolchain, you should be pointing to where
699 it is installed (e.g. 692 it is installed (e.g.
@@ -702,11 +695,10 @@
702 "<link linkend='sdk-installing-the-sdk'>Installing the SDK</link>" 695 "<link linkend='sdk-installing-the-sdk'>Installing the SDK</link>"
703 section for information about how the SDK is 696 section for information about how the SDK is
704 installed.</para> 697 installed.</para>
698
705 <para>If you are using a build system 699 <para>If you are using a build system
706 derived toolchain, the path you provide for 700 derived toolchain, the path you provide for
707 the 701 the "Toolchain Root Location" field is the
708 <filename>Toolchain Root Location</filename>
709 field is the
710 <ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink> 702 <ulink url='&YOCTO_DOCS_REF_URL;#build-directory'>Build Directory</ulink>
711 from which you run the 703 from which you run the
712 <filename>bitbake</filename> command (e.g 704 <filename>bitbake</filename> command (e.g
@@ -717,11 +709,11 @@
717 section. 709 section.
718 </para></listitem> 710 </para></listitem>
719 <listitem><para> 711 <listitem><para>
720 <emphasis>Specify Sysroot Location: 712 <emphasis>Specify Sysroot Location:</emphasis>
721 </emphasis>
722 This location is where the root filesystem 713 This location is where the root filesystem
723 for the target hardware resides. 714 for the target hardware resides.
724 </para> 715 </para>
716
725 <para>This location depends on where you 717 <para>This location depends on where you
726 separately extracted and installed the 718 separately extracted and installed the
727 target filesystem when you either built 719 target filesystem when you either built
@@ -743,6 +735,7 @@
743 directory (e.g. 735 directory (e.g.
744 <filename>/home/scottrif/poky/build/MY_QEMU_ROOTFS</filename>). 736 <filename>/home/scottrif/poky/build/MY_QEMU_ROOTFS</filename>).
745 </para> 737 </para>
738
746 <para>For more information on how to 739 <para>For more information on how to
747 install the toolchain and on how to extract 740 install the toolchain and on how to extract
748 and install the sysroot filesystem, see the 741 and install the sysroot filesystem, see the
@@ -750,12 +743,10 @@
750 section. 743 section.
751 </para></listitem> 744 </para></listitem>
752 <listitem><para> 745 <listitem><para>
753 <emphasis>Select the Target Architecture: 746 <emphasis>Select the Target Architecture:</emphasis>
754 </emphasis>
755 The target architecture is the type of 747 The target architecture is the type of
756 hardware you are going to use or emulate. 748 hardware you are going to use or emulate.
757 Use the pull-down 749 Use the pull-down "Target Architecture"
758 <filename>Target Architecture</filename>
759 menu to make your selection. 750 menu to make your selection.
760 The pull-down menu should have the 751 The pull-down menu should have the
761 supported architectures. 752 supported architectures.
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2026-01-31 21:20:35 +0000