diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2013-03-29 09:30:27 -0700 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-04-04 14:13:43 +0100 |
commit | b866355f61edff7097b1bd1d402b21c3dbc6c9b1 (patch) | |
tree | 741eedd9d98061594e2e64d7084e90f27c610d65 /documentation/ref-manual/faq.xml | |
parent | 59bc5009a081456aea5f86d42aec3526094af7ed (diff) | |
download | openembedded-core-contrib-b866355f61edff7097b1bd1d402b21c3dbc6c9b1.tar.gz |
ref-manual: Edits to the using an external toolchain question.
(From yocto-docs rev: 8fc82c1dfc527cf8356bed580077cb9e6f665876)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/faq.xml')
-rw-r--r-- | documentation/ref-manual/faq.xml | 44 |
1 files changed, 30 insertions, 14 deletions
diff --git a/documentation/ref-manual/faq.xml b/documentation/ref-manual/faq.xml index aca452cf73..d07f1e4012 100644 --- a/documentation/ref-manual/faq.xml +++ b/documentation/ref-manual/faq.xml @@ -514,30 +514,46 @@ <para> The toolchain configuration is very flexible and customizable. It is primarily controlled with the - <filename><link linkend='var-TCMODE'>TCMODE</link></filename> variable. - This variable controls which <filename>tcmode-*.inc</filename> file to include - from the <filename>meta/conf/distro/include</filename> directory within the - <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>source directory</ulink>. + <filename><link linkend='var-TCMODE'>TCMODE</link></filename> + variable. + This variable controls which <filename>tcmode-*.inc</filename> + file to include from the + <filename>meta/conf/distro/include</filename> directory within + the + <ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>. </para> <para> The default value of <filename>TCMODE</filename> is "default" (i.e. <filename>tcmode-default.inc</filename>). However, other patterns are accepted. - In particular, "external-*" refers to external toolchains of which there are some - basic examples included in the OpenEmbedded Core (<filename>meta</filename>). - You can use your own custom toolchain definition in your own layer - (or as defined in the <filename>local.conf</filename> file) at the location + In particular, "external-*" refers to external toolchains of + which there are some basic examples included in the + OpenEmbedded Core (<filename>meta</filename>). + You can use your own custom toolchain definition in your own + layer (or as defined in the <filename>local.conf</filename> + file) at the location <filename>conf/distro/include/tcmode-*.inc</filename>. </para> <para> - In addition to the toolchain configuration, you also need a corresponding toolchain recipe file. - This recipe file needs to package up any pre-built objects in the toolchain such as - <filename>libgcc</filename>, <filename>libstdcc++</filename>, - any locales, and <filename>libc</filename>. - An example is the <filename>external-sourcery-toolchain.bb</filename>, which is located - in <filename>meta/recipes-core/meta/</filename> within the source directory. + In addition to the toolchain configuration, you also need a + corresponding toolchain recipe file. + This recipe file needs to package up any pre-built objects in + the toolchain such as <filename>libgcc</filename>, + <filename>libstdcc++</filename>, any locales, and + <filename>libc</filename>. + An example is the + <filename>external-sourcery-toolchain.bb</filename>, which is + located in <filename>meta/recipes-core/meta/</filename> within + the Source Directory. + </para> + + <para> + For information on installing and using cross-development + toolchains, see the + "<ulink url='&YOCTO_DOCS_ADT_URL;#installing-the-adt'>Installing the ADT and Toolchains</ulink>" + section in the Yocto Project Application Developer's Guide. </para> </answer> </qandaentry> |