diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 90033539aa..ce843127e7 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -5932,7 +5932,6 @@
core-image-minimal
core-image-sato
meta-toolchain
- adt-installer
meta-ide-support
diff --git a/documentation/dev-manual/dev-manual-newbie.xml b/documentation/dev-manual/dev-manual-newbie.xml
index bf454c47ab..d72764d56b 100644
--- a/documentation/dev-manual/dev-manual-newbie.xml
+++ b/documentation/dev-manual/dev-manual-newbie.xml
@@ -636,8 +636,6 @@
A relocatable toolchain used outside of
BitBake by developers when developing applications
that will run on a targeted device.
- Sometimes this relocatable cross-development
- toolchain is referred to as the meta-toolchain.
@@ -666,10 +664,6 @@
"BSP Layers"
section in the Yocto Project Board Support Packages (BSP)
Developer's Guide.
- Meta-Toolchain:
- A term sometimes used for
- Cross-Development Toolchain.
- Metadata:
The files that BitBake parses when building an image.
In general, Metadata includes recipes, classes, and
diff --git a/documentation/profile-manual/profile-manual-usage.xml b/documentation/profile-manual/profile-manual-usage.xml
index 43c809dada..6a5657b241 100644
--- a/documentation/profile-manual/profile-manual-usage.xml
+++ b/documentation/profile-manual/profile-manual-usage.xml
@@ -2171,6 +2171,14 @@
You can now run 'bitbake <target>'
+ 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'
+
Once you've done that, you can cd to whatever directory
contains your scripts and use 'crosstap' to run the script:
diff --git a/documentation/ref-manual/introduction.xml b/documentation/ref-manual/introduction.xml
index 30620a6e59..b2b1fd8eff 100644
--- a/documentation/ref-manual/introduction.xml
+++ b/documentation/ref-manual/introduction.xml
@@ -591,8 +591,8 @@
Nightly Builds: These
tarball releases are available at
.
- 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.
Yocto Project Website: You can
find tarball releases of the Yocto Project and supported BSPs
diff --git a/documentation/ref-manual/ref-images.xml b/documentation/ref-manual/ref-images.xml
index b09d65cf3b..69b58f6ab4 100644
--- a/documentation/ref-manual/ref-images.xml
+++ b/documentation/ref-manual/ref-images.xml
@@ -80,7 +80,7 @@
core-image-lsb-sdk:
A core-image-lsb 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. poky-lsb).
@@ -114,7 +114,7 @@
tools appropriate for real-time use.core-image-rt-sdk:
A core-image-rt image that includes everything in
- meta-toolchain.
+ 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.
@@ -132,7 +132,8 @@
This image was formerly core-image-sdk.
core-image-sato-sdk:
- A core-image-sato image that includes everything in meta-toolchain.
+ A core-image-sato 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.core-image-testmaster:
diff --git a/documentation/ref-manual/ref-structure.xml b/documentation/ref-manual/ref-structure.xml
index 249fdef6c5..a0b36f034b 100644
--- a/documentation/ref-manual/ref-structure.xml
+++ b/documentation/ref-manual/ref-structure.xml
@@ -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'
diff --git a/documentation/ref-manual/usingpoky.xml b/documentation/ref-manual/usingpoky.xml
index 09ecaafda5..a7bf32d451 100644
--- a/documentation/ref-manual/usingpoky.xml
+++ b/documentation/ref-manual/usingpoky.xml
@@ -802,8 +802,8 @@
Build history collects similar information on the contents
- of SDKs (e.g. meta-toolchain
- or bitbake -c populate_sdk imagename)
+ of SDKs
+ (e.g. bitbake -c populate_sdk imagename)
as compared to information it collects for images.
Furthermore, this information differs depending on whether an
extensible or standard SDK is being produced.