diff options
| author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-07-13 10:38:29 -0700 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-07-17 10:54:08 +0100 |
| commit | 30f491637c9e4d366eef6cfe2e7e3966d02f3bd7 (patch) | |
| tree | 6340cd0878fe3628352b58f8bf86b0aede77e406 | |
| parent | 7f998daf7ea4629ac8d4df64eb13493d3aa9979d (diff) | |
| download | poky-30f491637c9e4d366eef6cfe2e7e3966d02f3bd7.tar.gz | |
documentation/poky-ref-manual/faq.xml: Updates to external toolchain
Updated the FAQ entry on "How do I use an external toolchain."
Comments were from Richard Purdie.
(From yocto-docs rev: db3986d2eff17087eb141ac0f4dfed55ff753368)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
| -rw-r--r-- | documentation/poky-ref-manual/faq.xml | 16 |
1 files changed, 9 insertions, 7 deletions
diff --git a/documentation/poky-ref-manual/faq.xml b/documentation/poky-ref-manual/faq.xml index 74406ffcb8..d619056355 100644 --- a/documentation/poky-ref-manual/faq.xml +++ b/documentation/poky-ref-manual/faq.xml | |||
| @@ -477,25 +477,27 @@ | |||
| 477 | <filename><link linkend='var-TCMODE'>TCMODE</link></filename> variable. | 477 | <filename><link linkend='var-TCMODE'>TCMODE</link></filename> variable. |
| 478 | This variable controls which <filename>tcmode-*.inc</filename> file to include | 478 | This variable controls which <filename>tcmode-*.inc</filename> file to include |
| 479 | from the <filename>meta/conf/distro/include</filename> directory within the | 479 | from the <filename>meta/conf/distro/include</filename> directory within the |
| 480 | <ulink url='&YOCTO_DOCS_DEV_URL;#yocto-project-files'>Yocto Project Files</ulink>. | 480 | <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>. |
| 481 | </para> | 481 | </para> |
| 482 | |||
| 482 | <para> | 483 | <para> |
| 483 | The default value of <filename>TCMODE</filename> is "default" | 484 | The default value of <filename>TCMODE</filename> is "default" |
| 484 | (i.e. <filename>tcmode-default.inc</filename>. | 485 | (i.e. <filename>tcmode-default.inc</filename>). |
| 485 | However, other patterns are accepted. | 486 | However, other patterns are accepted. |
| 486 | In particular, "external-*" refers to external toolchains of which there are some | 487 | In particular, "external-*" refers to external toolchains of which there are some |
| 487 | basic examples included with the core. | 488 | basic examples included in the OpenEmbedded Core (<filename>meta</filename>). |
| 488 | A user can use their own custom toolchain definition in their own layer | 489 | You can use your own custom toolchain definition in your own layer |
| 489 | (or as defined in the <filename>local.conf</filename> file) at the location | 490 | (or as defined in the <filename>local.conf</filename> file) at the location |
| 490 | <filename>conf/distro/include/tcmode-*.inc</filename>. | 491 | <filename>conf/distro/include/tcmode-*.inc</filename>. |
| 491 | </para> | 492 | </para> |
| 493 | |||
| 492 | <para> | 494 | <para> |
| 493 | In addition to the toolchain configuration, you also need a corresponding toolchain recipe file. | 495 | In addition to the toolchain configuration, you also need a corresponding toolchain recipe file. |
| 494 | This recipe file needs to package up any pre-built objects in the toolchain such as | 496 | This recipe file needs to package up any pre-built objects in the toolchain such as |
| 495 | <filename>libgcc</filename>, <filename>libstdcc++</filename>, | 497 | <filename>libgcc</filename>, <filename>libstdcc++</filename>, |
| 496 | any locales and <filename>libc</filename>. | 498 | any locales, and <filename>libc</filename>. |
| 497 | An example is the <filename>external-csl-toolchain_2008q3-72.bb</filename>, which reuses the core | 499 | An example is the <filename>external-sourcery-toolchain.bb</filename>, which is located |
| 498 | <filename>libc</filename> packaging class to do most of the work. | 500 | in <filename>meta/recipes-core/meta/</filename> within the source directory. |
| 499 | </para> | 501 | </para> |
| 500 | </answer> | 502 | </answer> |
| 501 | </qandaentry> | 503 | </qandaentry> |
