sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

dev-manual, profile-manual, ref-manual: Updates to remove meta-toolchain 

The term "meta-toolchain" is legacy now.  I went through and removed
its use except for where it appears still as output from the
oe-init-build-env script.

(From yocto-docs rev: 1cc134060459278997d57f1293f54091c5404d85)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2016-03-21 15:04:06 -07:00 committed by Richard Purdie
parent 7233e359dd
commit c3946bcaa6
7 changed files with 16 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
documentation/dev-manual/dev-manual-common-tasks.xml
View File

@ -5932,7 +5932,6 @@
core-image-minimal core-image-minimal
core-image-sato core-image-sato
meta-toolchain meta-toolchain
adt-installer
meta-ide-support meta-ide-support
</literallayout> </literallayout>
</para> </para>

6
documentation/dev-manual/dev-manual-newbie.xml
View File

@ -636,8 +636,6 @@
<listitem><para>A relocatable toolchain used outside of <listitem><para>A relocatable toolchain used outside of
BitBake by developers when developing applications BitBake by developers when developing applications
that will run on a targeted device. that will run on a targeted device.
Sometimes this relocatable cross-development
toolchain is referred to as the meta-toolchain.
</para></listitem> </para></listitem>
</itemizedlist> </itemizedlist>
</para> </para>
@ -666,10 +664,6 @@
"<ulink url='&YOCTO_DOCS_BSP_URL;#bsp-layers'>BSP Layers</ulink>" "<ulink url='&YOCTO_DOCS_BSP_URL;#bsp-layers'>BSP Layers</ulink>"
section in the Yocto Project Board Support Packages (BSP) section in the Yocto Project Board Support Packages (BSP)
Developer's Guide.</para></listitem> Developer's Guide.</para></listitem>
<listitem><para id='meta-toolchain'><emphasis>Meta-Toolchain:</emphasis>
A term sometimes used for
<link linkend='cross-development-toolchain'>Cross-Development Toolchain</link>.
</para></listitem>
<listitem><para id='metadata'><emphasis>Metadata:</emphasis> <listitem><para id='metadata'><emphasis>Metadata:</emphasis>
The files that BitBake parses when building an image. The files that BitBake parses when building an image.
In general, Metadata includes recipes, classes, and In general, Metadata includes recipes, classes, and

8
documentation/profile-manual/profile-manual-usage.xml
View File

@ -2171,6 +2171,14 @@
You can now run 'bitbake &lt;target&gt;' You can now run 'bitbake &lt;target&gt;'
Common targets are:
core-image-minimal
core-image-sato
meta-toolchain
meta-ide-support
You can also run generated qemu images with a command like 'runqemu qemux86'
</literallayout> </literallayout>
Once you've done that, you can cd to whatever directory Once you've done that, you can cd to whatever directory
contains your scripts and use 'crosstap' to run the script: contains your scripts and use 'crosstap' to run the script:

4
documentation/ref-manual/introduction.xml
View File

@ -591,8 +591,8 @@
<listitem><para><emphasis>Nightly Builds:</emphasis> These <listitem><para><emphasis>Nightly Builds:</emphasis> These
tarball releases are available at tarball releases are available at
<ulink url='&YOCTO_AB_NIGHTLY_URL;'/>. <ulink url='&YOCTO_AB_NIGHTLY_URL;'/>.
These builds include Yocto Project releases, meta-toolchain These builds include Yocto Project releases, SDK installation
tarball installation scripts, and experimental builds. scripts, and experimental builds.
</para></listitem> </para></listitem>
<listitem><para><emphasis>Yocto Project Website:</emphasis> You can <listitem><para><emphasis>Yocto Project Website:</emphasis> You can
find tarball releases of the Yocto Project and supported BSPs find tarball releases of the Yocto Project and supported BSPs

7
documentation/ref-manual/ref-images.xml
View File

@ -80,7 +80,7 @@
</para></listitem> </para></listitem>
<listitem><para><filename>core-image-lsb-sdk</filename>: <listitem><para><filename>core-image-lsb-sdk</filename>:
A <filename>core-image-lsb</filename> that includes everything in A <filename>core-image-lsb</filename> that includes everything in
meta-toolchain but also includes development headers and libraries the cross-toolchain but also includes development headers and libraries
to form a complete standalone SDK. to form a complete standalone SDK.
This image requires a distribution configuration that This image requires a distribution configuration that
enables LSB compliance (e.g. <filename>poky-lsb</filename>). enables LSB compliance (e.g. <filename>poky-lsb</filename>).
@ -114,7 +114,7 @@
tools appropriate for real-time use.</para></listitem> tools appropriate for real-time use.</para></listitem>
<listitem><para><filename>core-image-rt-sdk</filename>: <listitem><para><filename>core-image-rt-sdk</filename>:
A <filename>core-image-rt</filename> image that includes everything in A <filename>core-image-rt</filename> image that includes everything in
<filename>meta-toolchain</filename>. the cross-toolchain.
The image also includes development headers and libraries to form a complete The image also includes development headers and libraries to form a complete
stand-alone SDK and is suitable for development using the target. stand-alone SDK and is suitable for development using the target.
</para></listitem> </para></listitem>
@ -132,7 +132,8 @@
This image was formerly <filename>core-image-sdk</filename>. This image was formerly <filename>core-image-sdk</filename>.
</para></listitem> </para></listitem>
<listitem><para><filename>core-image-sato-sdk</filename>: <listitem><para><filename>core-image-sato-sdk</filename>:
A <filename>core-image-sato</filename> image that includes everything in meta-toolchain. A <filename>core-image-sato</filename> image that includes everything in
the cross-toolchain.
The image also includes development headers and libraries to form a complete standalone SDK The image also includes development headers and libraries to form a complete standalone SDK
and is suitable for development using the target.</para></listitem> and is suitable for development using the target.</para></listitem>
<listitem><para><filename>core-image-testmaster</filename>: <listitem><para><filename>core-image-testmaster</filename>:

2
documentation/ref-manual/ref-structure.xml
View File

@ -227,7 +227,6 @@
core-image-minimal core-image-minimal
core-image-sato core-image-sato
meta-toolchain meta-toolchain
adt-installer
meta-ide-support meta-ide-support
You can also run generated qemu images with a command like 'runqemu qemux86' You can also run generated qemu images with a command like 'runqemu qemux86'
@ -366,7 +365,6 @@
core-image-minimal core-image-minimal
core-image-sato core-image-sato
meta-toolchain meta-toolchain
adt-installer
meta-ide-support meta-ide-support
You can also run generated qemu images with a command like 'runqemu qemux86' You can also run generated qemu images with a command like 'runqemu qemux86'

4
documentation/ref-manual/usingpoky.xml
View File

@ -802,8 +802,8 @@
<para> <para>
Build history collects similar information on the contents Build history collects similar information on the contents
of SDKs (e.g. <filename>meta-toolchain</filename> of SDKs
or <filename>bitbake -c populate_sdk imagename</filename>) (e.g. <filename>bitbake -c populate_sdk imagename</filename>)
as compared to information it collects for images. as compared to information it collects for images.
Furthermore, this information differs depending on whether an Furthermore, this information differs depending on whether an
extensible or standard SDK is being produced. extensible or standard SDK is being produced.