mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-05-09 05:29:32 +00:00
Code Issues Projects Releases Wiki Activity

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

Browse Source 
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
Download Patch File Download Diff File Expand all files Collapse all files
documentation/ref-manual/introduction.xml
+2 -2
View File
@@ -591,8 +591,8 @@
<listitem><para><emphasis>Nightly Builds:</emphasis> These
tarball releases are available at
<ulink url='&YOCTO_AB_NIGHTLY_URL;'/>.
These builds include Yocto Project releases, meta-toolchain
tarball installation scripts, and experimental builds.
These builds include Yocto Project releases, SDK installation
scripts, and experimental builds.
</para></listitem>
<listitem><para><emphasis>Yocto Project Website:</emphasis> You can
find tarball releases of the Yocto Project and supported BSPs
documentation/ref-manual/ref-images.xml
+4 -3
View File
@@ -80,7 +80,7 @@
</para></listitem>
<listitem><para><filename>core-image-lsb-sdk</filename>:
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.
This image requires a distribution configuration that
enables LSB compliance (e.g. <filename>poky-lsb</filename>).
@@ -114,7 +114,7 @@
tools appropriate for real-time use.</para></listitem>
<listitem><para><filename>core-image-rt-sdk</filename>:
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
stand-alone SDK and is suitable for development using the target.
</para></listitem>
@@ -132,7 +132,8 @@
This image was formerly <filename>core-image-sdk</filename>.
</para></listitem>
<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
and is suitable for development using the target.</para></listitem>
<listitem><para><filename>core-image-testmaster</filename>:
documentation/ref-manual/ref-structure.xml
-2
View File
@@ -227,7 +227,6 @@
core-image-minimal
core-image-sato
meta-toolchain
adt-installer
meta-ide-support
You can also run generated qemu images with a command like 'runqemu qemux86'
@@ -366,7 +365,6 @@
core-image-minimal
core-image-sato
meta-toolchain
adt-installer
meta-ide-support
You can also run generated qemu images with a command like 'runqemu qemux86'
documentation/ref-manual/usingpoky.xml
+2 -2
View File
@@ -802,8 +802,8 @@
<para>
Build history collects similar information on the contents
of SDKs (e.g. <filename>meta-toolchain</filename>
or <filename>bitbake -c populate_sdk imagename</filename>)
of SDKs
(e.g. <filename>bitbake -c populate_sdk imagename</filename>)
as compared to information it collects for images.
Furthermore, this information differs depending on whether an
extensible or standard SDK is being produced.