<para>
As a result of the build process "helloworld", "helloworld-dbg" and "hellworld-dev"
- packages will be built by default. You can <link linkend='usingpoky-extend-addpkg-files'>
- control package process</link> yourself.
+ packages will be built by default. It is possible to<link linkend='usingpoky-extend-addpkg-files'>
+ customise the packaging process</link>.
</para>
</section>
</para>
<programlisting>
pkg_postinst_PACKAGENAME () {
- #!/bin/sh -e
- # Commands to carry out
+#!/bin/sh -e
+# Commands to carry out
}
</programlisting>
<para>
<programlisting>
pkg_postinst_PACKAGENAME () {
- #!/bin/sh -e
- if [ x"$D" = "x" ]; then
- # Actions to carry out on the device go here
- else
- exit 1
- fi
+#!/bin/sh -e
+if [ x"$D" = "x" ]; then
+ # Actions to carry out on the device go here
+else
+ exit 1
+fi
}
</programlisting>
variable. To create these, the best reference is <filename>meta/classes/poky-image.bbclass</filename>
which illustrates how poky achieves this. In summary, the file looks at the contents of the
<glossterm><link linkend='var-IMAGE_FEATURES'>IMAGE_FEATURES</link></glossterm>
- variable and then map into a set of tasks or packages. Based on this then the
+ variable and then maps this into a set of tasks or packages. Based on this then the
<glossterm><link linkend='var-IMAGE_INSTALL'> IMAGE_INSTALL</link></glossterm>
variable is generated automatically. Extra features can be added by
extending the class or creating a custom class for use with specialised image .bb files.
<para>
The Poky tree includes several additional layers which demonstrate
- this functionality, such as meta-moblin, meta-emenlow, meta-extras.
- Default layers enabled are meta-moblin and meta-emenlow, which may
- suffer from future changes. The meta-extras repostory is not enabled
- by default but enabling any layer is as easy as adding the layers path
- to the BBLAYERS variable in your bblayers.conf. this is how meta-extras
- are enabled in Poky builds:
+ this functionality, such as meta-emenlow and meta-extras.
+ The meta-emenlow layer is an example layer enabled by default. The meta-extras
+ repostory is not enabled by default but enabling any layer is as easy as adding
+ the layers path to the BBLAYERS variable in your bblayers.conf. this is how
+ meta-extras are enabled in Poky builds:
</para>
<para>
<literallayout class='monospaced'>LCONF_VERSION = "1"
</para>
<para>
- Emenlow bbclasses and configuration are added to the BBPATH
+ Additional bbclass and configuration files can be locationed by
+ bitbake through the addition to the BBPATH
environment variable. In this case, the first file with the
matching name found in BBPATH is the one that is used, just
like the PATH variable for binaries. It is therefore recommended
They usually happen at preset times such as at night when the machine
load isn't high from the incremental builds.
<ulink url='http://autobuilder.pokylinux.org:8010'>poky autobuilder</ulink>
- is an example implementation with buildrot.
+ is an example implementation with buildbot.
</para>
<para>
"-f" or "--force" is used to force re-execution of the specified task.
Other tasks may also be called this way. But note that all the modifications
in <glossterm><link linkend='var-WORKDIR'>WORKDIR</link></glossterm>
- are gone once you executes "-c clean" for a pacakge.
+ are gone once you executes "-c clean" for a package.
</para>
<section id='usingpoky-modifying-packages-quilt'>
<para>
This directory contains user configuration files and the output
- from Poky. It's now deprecated to be a sub-directory in Poky source tree,
- though it's still supported. The desired way is to use <link
- linkend='structure-core-script'>seperate output directory</link> for build
- outside of Poky source tree.
+ generated by Poky in its standard configuration where the source tree is
+ combined with the output. It is also possible to place output and configuration
+ files in a directory separate from the Poky source, see the section <link
+ linkend='structure-core-script'>seperate output directory</link>.
</para>
</section>
a shell makes changes to PATH and sets other core BitBake variables based on the
current working directory. You need to use this before running Poky commands.
Internally it uses scripts within the <filename class="directory">scripts/
- </filename> directory to do the bulk of the work. Now this script supports
+ </filename> directory to do the bulk of the work. This script supports
specifying any directory as the build output:
</para>
</programlisting>
<para>
- Above command can be typed from any directory, as long as POKY_SRC points to
+ The above command can be typed from any directory, as long as POKY_SRC points to
the desired Poky source tree. The optional BUILDDIR could be any directory you'd
- like to contain output contents.
+ like Poky to generate the build output into.
</para>
</section>
</section>
<para>
This file defines layers walked by bitbake. If there's no <filename>
bblayers.conf</filename> present, it is created from <filename>bblayers.conf.sample
- </filename>.
+ </filename> when the environment setup script is sourced.
</para>
</section>
