diff options
-rw-r--r-- | documentation/adt-manual/adt-prepare.xml | 17 | ||||
-rw-r--r-- | documentation/yocto-project-qs/yocto-project-qs.xml | 60 |
2 files changed, 51 insertions, 26 deletions
diff --git a/documentation/adt-manual/adt-prepare.xml b/documentation/adt-manual/adt-prepare.xml index f8ba557f39..6900b0cd8c 100644 --- a/documentation/adt-manual/adt-prepare.xml +++ b/documentation/adt-manual/adt-prepare.xml | |||
@@ -229,8 +229,10 @@ | |||
229 | <title>Using a Cross-Toolchain Tarball</title> | 229 | <title>Using a Cross-Toolchain Tarball</title> |
230 | 230 | ||
231 | <para> | 231 | <para> |
232 | If you want to simply install the cross-toolchain by hand, you can | 232 | If you want to simply install a cross-toolchain by hand, you can |
233 | do so by running the toolchain installer. | 233 | do so by running the toolchain installer. |
234 | The installer includes the pre-built cross-toolchain, the | ||
235 | <filename>runqemu</filename> script, and support files. | ||
234 | If you use this method to install the cross-toolchain, you | 236 | If you use this method to install the cross-toolchain, you |
235 | might still need to install the target sysroot by installing and | 237 | might still need to install the target sysroot by installing and |
236 | extracting it separately. | 238 | extracting it separately. |
@@ -241,25 +243,30 @@ | |||
241 | <para> | 243 | <para> |
242 | Follow these steps: | 244 | Follow these steps: |
243 | <orderedlist> | 245 | <orderedlist> |
244 | <listitem><para>Get the toolchain installer using one of the | 246 | <listitem><para>Get your toolchain installer using one of the |
245 | following methods: | 247 | following methods: |
246 | <itemizedlist> | 248 | <itemizedlist> |
247 | <listitem><para>Go to | 249 | <listitem><para>Go to |
248 | <ulink url='&YOCTO_TOOLCHAIN_DL_URL;'></ulink> | 250 | <ulink url='&YOCTO_TOOLCHAIN_DL_URL;'></ulink> |
249 | and find the folder that matches your host | 251 | and find the folder that matches your host |
250 | development system (i.e. <filename>i686</filename> | 252 | development system (i.e. <filename>i686</filename> |
251 | for 32-bit machines or <filename>x86-64</filename> | 253 | for 32-bit machines or <filename>x86_64</filename> |
252 | for 64-bit machines).</para> | 254 | for 64-bit machines).</para> |
253 | <para>Go into that folder and download the toolchain | 255 | <para>Go into that folder and download the toolchain |
254 | installer whose name includes the appropriate target | 256 | installer whose name includes the appropriate target |
255 | architecture. | 257 | architecture. |
258 | The toolchains provided by the Yocto Project | ||
259 | are based off of the | ||
260 | <filename>core-image-sato</filename> image and | ||
261 | contain libraries appropriate for developing | ||
262 | against that image. | ||
256 | For example, if your host development system is a | 263 | For example, if your host development system is a |
257 | 64-bit x86 system and you are going to use | 264 | 64-bit x86 system and you are going to use |
258 | your cross-toolchain for a 32-bit x86 | 265 | your cross-toolchain for a 32-bit x86 |
259 | target, go into the <filename>x86_64</filename> | 266 | target, go into the <filename>x86_64</filename> |
260 | folder and download the following installer: | 267 | folder and download the following installer: |
261 | <literallayout class='monospaced'> | 268 | <literallayout class='monospaced'> |
262 | poky-eglibc-x86_64-i586-toolchain-&DISTRO;.sh | 269 | poky-eglibc-x86_64-core-image-sato-i586.sh |
263 | </literallayout></para></listitem> | 270 | </literallayout></para></listitem> |
264 | <listitem><para>Build your own toolchain installer. | 271 | <listitem><para>Build your own toolchain installer. |
265 | For cases where you cannot use an installer | 272 | For cases where you cannot use an installer |
@@ -278,7 +285,7 @@ | |||
278 | The example assumes the toolchain installer is located | 285 | The example assumes the toolchain installer is located |
279 | in <filename>~/Downloads/</filename>. | 286 | in <filename>~/Downloads/</filename>. |
280 | <literallayout class='monospaced'> | 287 | <literallayout class='monospaced'> |
281 | $ ~/Downloads/poky-eglibc-x86_64-i586-toolchain-&DISTRO;.sh | 288 | $ ~/Downloads/poky-eglibc-x86_64-core-image-sato-i586.sh |
282 | </literallayout> | 289 | </literallayout> |
283 | <note> | 290 | <note> |
284 | If you do not have write permissions for the directory | 291 | If you do not have write permissions for the directory |
diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml index a8e8c3a35a..372a86efd0 100644 --- a/documentation/yocto-project-qs/yocto-project-qs.xml +++ b/documentation/yocto-project-qs/yocto-project-qs.xml | |||
@@ -552,44 +552,62 @@ | |||
552 | 552 | ||
553 | <section id='installing-the-toolchain'> | 553 | <section id='installing-the-toolchain'> |
554 | <title>Installing the Toolchain</title> | 554 | <title>Installing the Toolchain</title> |
555 | |||
555 | <para> | 556 | <para> |
556 | You can download a tarball installer, which includes the pre-built toolchain, the | 557 | You can download a tarball installer, which includes the |
557 | <filename>runqemu</filename> | 558 | pre-built toolchain, the <filename>runqemu</filename> |
558 | script, and support files from the appropriate directory under | 559 | script, and support files from the appropriate directory under |
559 | <ulink url='&YOCTO_TOOLCHAIN_DL_URL;'></ulink>. | 560 | <ulink url='&YOCTO_TOOLCHAIN_DL_URL;'></ulink>. |
560 | Toolchains are available for 32-bit and 64-bit x86 development systems from the | 561 | Toolchains are available for 32-bit and 64-bit x86 development |
561 | <filename>i686</filename> and <filename>x86_64</filename> directories, respectively. | 562 | systems from the <filename>i686</filename> and |
562 | Each type of development system supports five target architectures. | 563 | <filename>x86_64</filename> directories, respectively. |
563 | The names of the tarball installer scripts are such that a string representing the | 564 | The toolchains the Yocto Project provides are based off the |
564 | host system appears first in the filename and then is immediately followed by a | 565 | <filename>core-image-sato</filename> image and contain |
565 | string representing the target architecture. | 566 | libraries appropriate for developing against that image. |
567 | Each type of development system supports five or more target | ||
568 | architectures. | ||
569 | </para> | ||
570 | |||
571 | <para> | ||
572 | The names of the tarball installer scripts are such that a | ||
573 | string representing the host system appears first in the | ||
574 | filename and then is immediately followed by a string | ||
575 | that represents the target architecture. | ||
566 | </para> | 576 | </para> |
567 | 577 | ||
568 | <literallayout class='monospaced'> | 578 | <literallayout class='monospaced'> |
569 | poky-eglibc-<<emphasis>host_system</emphasis>>-<<emphasis>arch</emphasis>>-toolchain-gmae-<<emphasis>release</emphasis>>.sh | 579 | poky-eglibc-<<emphasis>host_system</emphasis>>-<<emphasis>image_type</emphasis>>-<<emphasis>arch</emphasis>>.sh |
570 | 580 | ||
571 | Where: | 581 | Where: |
572 | <<emphasis>host_system</emphasis>> is a string representing your development system: | 582 | <<emphasis>host_system</emphasis>> is a string representing your development system: |
573 | i686 or x86_64. | 583 | i686 or x86_64. |
574 | 584 | ||
575 | <<emphasis>arch</emphasis>> is a string representing the target architecture: | 585 | <<emphasis>image_type</emphasis>> is a string representing the image you wish to |
576 | i586, x86_64, powerpc, mips, or arm. | 586 | develop a Software Development Toolkit (SDK) for use against. |
587 | The Yocto Project builds toolchain installers using the | ||
588 | following BitBake command: | ||
589 | |||
590 | bitbake core-image-sato -c do_populatesdk core-image-sato | ||
577 | 591 | ||
578 | <<emphasis>release</emphasis>> is the version of Yocto Project. | 592 | <<emphasis>arch</emphasis>> is a string representing the tuned target architecture: |
593 | |||
594 | i586, x86_64, powerpc, mips, armv7a or armv5te | ||
579 | </literallayout> | 595 | </literallayout> |
580 | 596 | ||
581 | <para> | 597 | <para> |
582 | For example, the following toolchain installer is for a 64-bit development | 598 | For example, the following toolchain installer is for a 64-bit |
583 | host system and a 32-bit target architecture: | 599 | development host system and a i586-tuned target architecture |
600 | based off the SDK for <filename>core-image-sato</filename>: | ||
601 | <literallayout class='monospaced'> | ||
602 | poky-eglibc-x86_64-core-image-sato-i586.sh | ||
603 | </literallayout> | ||
584 | </para> | 604 | </para> |
585 | 605 | ||
586 | <literallayout class='monospaced'> | ||
587 | poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.sh | ||
588 | </literallayout> | ||
589 | |||
590 | <para> | 606 | <para> |
591 | Toolchains are self-contained and by default are installed into <filename>/opt/poky</filename>. | 607 | Toolchains are self-contained and by default are installed into |
592 | However, when you run the toolchain installer, you can choose an installation directory. | 608 | <filename>/opt/poky</filename>. |
609 | However, when you run the toolchain installer, you can choose an | ||
610 | installation directory. | ||
593 | </para> | 611 | </para> |
594 | 612 | ||
595 | <para> | 613 | <para> |
@@ -610,7 +628,7 @@ | |||
610 | 628 | ||
611 | <para> | 629 | <para> |
612 | <literallayout class='monospaced'> | 630 | <literallayout class='monospaced'> |
613 | $ ~/Downloads/poky-eglibc-x86_64-i586-toolchain-gmae-&DISTRO;.sh | 631 | $ ~/Downloads/poky-eglibc-x86_64-core-image-sato-i586.sh |
614 | </literallayout> | 632 | </literallayout> |
615 | </para> | 633 | </para> |
616 | 634 | ||