summaryrefslogtreecommitdiff
path: root/yocto-poky/documentation/ref-manual/ref-structure.xml
diff options
context:
space:
mode:
Diffstat (limited to 'yocto-poky/documentation/ref-manual/ref-structure.xml')
-rw-r--r--yocto-poky/documentation/ref-manual/ref-structure.xml37
1 files changed, 13 insertions, 24 deletions
diff --git a/yocto-poky/documentation/ref-manual/ref-structure.xml b/yocto-poky/documentation/ref-manual/ref-structure.xml
index 48e39212a..e51ceb1bf 100644
--- a/yocto-poky/documentation/ref-manual/ref-structure.xml
+++ b/yocto-poky/documentation/ref-manual/ref-structure.xml
@@ -123,8 +123,8 @@
</para>
</section>
- <section id='structure-core-meta-yocto'>
- <title><filename>meta-yocto/</filename></title>
+ <section id='structure-core-meta-poky'>
+ <title><filename>meta-poky/</filename></title>
<para>
This directory contains the configuration for the Poky
@@ -227,14 +227,13 @@
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'
</literallayout>
The script gets its default list of common targets from the
<filename>conf-notes.txt</filename> file, which is found in the
- <filename>meta-yocto</filename> directory within the
+ <filename>meta-poky</filename> directory within the
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
Should you have custom distributions, it is very easy to modify
this configuration file to include your targets for your
@@ -261,7 +260,7 @@
</literallayout>
The OpenEmbedded build system uses the template configuration
files, which are found by default in the
- <filename>meta-yocto/conf</filename> directory in the
+ <filename>meta-poky/conf</filename> directory in the
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
See the
"<ulink url='&YOCTO_DOCS_DEV_URL;#creating-a-custom-template-configuration-directory'>Creating a Custom Template Configuration Directory</ulink>"
@@ -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'
@@ -375,7 +373,7 @@
</literallayout>
The script gets its default list of common targets from the
<filename>conf-notes.txt</filename> file, which is found in the
- <filename>meta-yocto</filename> directory within the
+ <filename>meta-poky</filename> directory within the
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
Should you have custom distributions, it is very easy to modify
this configuration file to include your targets for your
@@ -411,7 +409,7 @@
<para>
The OpenEmbedded build system uses the template configuration
files, which are found by default in the
- <filename>meta-yocto/conf</filename> directory in the
+ <filename>meta-poky/conf</filename> directory in the
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
See the
"<ulink url='&YOCTO_DOCS_DEV_URL;#creating-a-custom-template-configuration-directory'>Creating a Custom Template Configuration Directory</ulink>"
@@ -515,7 +513,7 @@
<para>
The source <filename>local.conf.sample</filename> file used
depends on the <filename>$TEMPLATECONF</filename> script variable,
- which defaults to <filename>meta-yocto/conf</filename>
+ which defaults to <filename>meta-poky/conf</filename>
when you are building from the Yocto Project development
environment and defaults to <filename>meta/conf</filename> when
you are building from the OpenEmbedded Core environment.
@@ -538,7 +536,7 @@
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
You can find the Yocto Project version of the
<filename>local.conf.sample</filename> file in the
- <filename>meta-yocto/conf</filename> directory.
+ <filename>meta-poky/conf</filename> directory.
</note>
</para>
</section>
@@ -569,7 +567,7 @@
<para>
The source <filename>bblayers.conf.sample</filename> file used
depends on the <filename>$TEMPLATECONF</filename> script variable,
- which defaults to <filename>meta-yocto/conf</filename>
+ which defaults to <filename>meta-poky/conf</filename>
when you are building from the Yocto Project development
environment and defaults to <filename>meta/conf</filename> when
you are building from the OpenEmbedded Core environment.
@@ -590,7 +588,7 @@
<ulink url='&YOCTO_DOCS_DEV_URL;#source-directory'>Source Directory</ulink>.
You can find the Yocto Project version of the
<filename>bblayers.conf.sample</filename> file in the
- <filename>meta-yocto/conf</filename> directory.
+ <filename>meta-poky/conf</filename> directory.
</note>
</para>
</section>
@@ -738,8 +736,7 @@
<para>
Be careful when deleting files in this directory.
You can safely delete old images from this directory (e.g.
- <filename>core-image-*</filename>, <filename>hob-image-*</filename>,
- etc.).
+ <filename>core-image-*</filename>).
However, the kernel (<filename>*zImage*</filename>, <filename>*uImage*</filename>, etc.),
bootloader and other supplementary files might be deployed here prior to building an
image.
@@ -767,8 +764,8 @@
toolchain installer scripts, which when executed, install the
sysroot that matches your target hardware.
You can find out more about these installers in the
- "<ulink url='&YOCTO_DOCS_ADT_URL;#optionally-building-a-toolchain-installer'>Optionally Building a Toolchain Installer</ulink>"
- section in the Yocto Project Application Developer's Guide.
+ "<ulink url='&YOCTO_DOCS_SDK_URL;#sdk-building-an-sdk-installer'>Building an SDK Installer</ulink>"
+ section in the Yocto Project Software Development Kit (SDK) Developer's Guide.
</para>
</section>
@@ -1091,14 +1088,6 @@
</para>
</section>
- <section id='structure-meta-recipes-qt'>
- <title><filename>meta/recipes-qt/</filename></title>
-
- <para>
- This directory contains all things related to the Qt application framework.
- </para>
- </section>
-
<section id='structure-meta-recipes-rt'>
<title><filename>meta/recipes-rt/</filename></title>