Layers
- The source directory contains several layers right out of the box.
- You can easily identify a layer in the source directory by its folder name.
+ The Source Directory contains several layers right out of the box.
+ You can easily identify a layer in the Source Directory by its folder name.
Folders that are layers begin with the string meta.
- For example, when you set up the source directory
+ For example, when you set up the Source Directory
structure, you will see several layers: meta,
meta-hob, meta-skeleton,
meta-yocto, and meta-yocto-bsp.
@@ -174,14 +174,14 @@
If this is the case, you need to address that deficiency instead of overlaying
the include file.
For example, consider how Qt 4 database support plug-ins are configured.
- The source directory does not have
+ The Source Directory does not have
MySQL or PostgreSQL, however OpenEmbedded's
layer meta-oe does.
Consequently, meta-oe uses .bbappend
files to modify the QT_SQL_DRIVER_FLAGS variable to enable
the appropriate plugins.
This variable was added to the qt4.inc include file in
- the source directory specifically to allow the meta-oe layer
+ the Source Directory specifically to allow the meta-oe layer
to be able to control which plugins are built.
@@ -193,9 +193,9 @@
meta-<layer_name> format.
Clone the repository alongside other meta
directories in the
- source directory.
+ Source Directory.
- Following these recommendations keeps your source directory and
+ Following these recommendations keeps your Source Directory and
its configuration entirely inside the Yocto Project's core base.
@@ -283,7 +283,7 @@
As an example, consider the main formfactor recipe and a corresponding formfactor
append file both from the
- source directory.
+ Source Directory.
Here is the main formfactor recipe, which is named formfactor_0.0.bb and
located in the meta layer at meta/recipes-bsp/formfactor:
@@ -580,7 +580,7 @@
with specialized image .bb files.
You can also add more features by configuring the
EXTRA_IMAGE_FEATURES
- variable in the local.conf file found in the source directory
+ variable in the local.conf file found in the Source Directory
located in the build directory.
@@ -1083,7 +1083,7 @@
You need to either create a new kernel recipe for this machine, or extend an
existing recipe.
You can find several kernel examples in the
- source directory at meta/recipes-kernel/linux
+ Source Directory at meta/recipes-kernel/linux
that you can use as references.
@@ -1206,7 +1206,7 @@
extended to support multiple libraries.
Many standard recipes are already extended and support multiple libraries.
You can check in the meta/conf/multilib.conf
- configuration file in the source directory to see how this is
+ configuration file in the Source Directory to see how this is
done using the
BBCLASSEXTEND
variable.
@@ -1365,7 +1365,7 @@
script found in the
Build Directory.
The following commands build and invoke menuconfig assuming the
- source directory top-level folder is ~/poky:
+ Source Directory top-level folder is ~/poky:
$ cd ~/poky
$ source oe-init-build-env
@@ -2013,7 +2013,7 @@
$ bitbake world -f -c distro_check
The results are stored in the build/tmp/log/distro_check-${DATETIME}.results
- file found in the source directory.
+ file found in the Source Directory.
@@ -2029,7 +2029,7 @@
Situations exist where you might want to build software from source files that are external to
- and thus outside of the source directory.
+ and thus outside of the Source Directory.
For example, suppose you have a project that includes a new BSP with a heavily customized
kernel, a very minimal image, and some new user-space recipes.
And, you want to minimize exposing the build system to the