<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;#yocto-project-files'>Yocto Project Files</ulink>.
+ <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>.
+ (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 with the core.
- A user can use their own custom toolchain definition in their own layer
+ 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-csl-toolchain_2008q3-72.bb</filename>, which reuses the core
- <filename>libc</filename> packaging class to do most of the work.
+ 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>
</answer>
</qandaentry>