handbook: Various minor fixes
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
This commit is contained in:
parent
0a217cd18f
commit
ad30f2cc4e
|
@ -74,8 +74,8 @@ do_install() {
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
As a result of the build process "helloworld", "helloworld-dbg" and "hellworld-dev"
|
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'>
|
packages will be built by default. It is possible to<link linkend='usingpoky-extend-addpkg-files'>
|
||||||
control package process</link> yourself.
|
customise the packaging process</link>.
|
||||||
</para>
|
</para>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
|
@ -398,7 +398,7 @@ RRECOMMENDS_task-custom-tools = "\
|
||||||
variable. To create these, the best reference is <filename>meta/classes/poky-image.bbclass</filename>
|
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
|
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>
|
<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>
|
<glossterm><link linkend='var-IMAGE_INSTALL'> IMAGE_INSTALL</link></glossterm>
|
||||||
variable is generated automatically. Extra features can be added by
|
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.
|
extending the class or creating a custom class for use with specialised image .bb files.
|
||||||
|
@ -586,12 +586,11 @@ DISPLAY_SUBPIXEL_ORDER=vrgb
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
The Poky tree includes several additional layers which demonstrate
|
The Poky tree includes several additional layers which demonstrate
|
||||||
this functionality, such as meta-moblin, meta-emenlow, meta-extras.
|
this functionality, such as meta-emenlow and meta-extras.
|
||||||
Default layers enabled are meta-moblin and meta-emenlow, which may
|
The meta-emenlow layer is an example layer enabled by default. The meta-extras
|
||||||
suffer from future changes. The meta-extras repostory is not enabled
|
repostory is not enabled by default but enabling any layer is as easy as adding
|
||||||
by default but enabling any layer is as easy as adding the layers path
|
the layers path to the BBLAYERS variable in your bblayers.conf. this is how
|
||||||
to the BBLAYERS variable in your bblayers.conf. this is how meta-extras
|
meta-extras are enabled in Poky builds:
|
||||||
are enabled in Poky builds:
|
|
||||||
</para>
|
</para>
|
||||||
<para>
|
<para>
|
||||||
<literallayout class='monospaced'>LCONF_VERSION = "1"
|
<literallayout class='monospaced'>LCONF_VERSION = "1"
|
||||||
|
@ -650,7 +649,8 @@ BBFILE_PRIORITY_emenlow = "6"
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<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
|
environment variable. In this case, the first file with the
|
||||||
matching name found in BBPATH is the one that is used, just
|
matching name found in BBPATH is the one that is used, just
|
||||||
like the PATH variable for binaries. It is therefore recommended
|
like the PATH variable for binaries. It is therefore recommended
|
||||||
|
@ -773,7 +773,7 @@ BBFILE_PRIORITY_emenlow = "6"
|
||||||
They usually happen at preset times such as at night when the machine
|
They usually happen at preset times such as at night when the machine
|
||||||
load isn't high from the incremental builds.
|
load isn't high from the incremental builds.
|
||||||
<ulink url='http://autobuilder.pokylinux.org:8010'>poky autobuilder</ulink>
|
<ulink url='http://autobuilder.pokylinux.org:8010'>poky autobuilder</ulink>
|
||||||
is an example implementation with buildrot.
|
is an example implementation with buildbot.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
|
@ -856,7 +856,7 @@ bitbake -c compile -f NAME_OF_PACKAGE
|
||||||
"-f" or "--force" is used to force re-execution of the specified task.
|
"-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
|
Other tasks may also be called this way. But note that all the modifications
|
||||||
in <glossterm><link linkend='var-WORKDIR'>WORKDIR</link></glossterm>
|
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>
|
</para>
|
||||||
|
|
||||||
<section id='usingpoky-modifying-packages-quilt'>
|
<section id='usingpoky-modifying-packages-quilt'>
|
||||||
|
|
|
@ -60,7 +60,7 @@
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
'do_configure' regenearates the configure script and (using autoreconf)
|
'do_configure' regenearates the configure script (using autoreconf) and
|
||||||
then launches it with a standard set of arguments used during
|
then launches it with a standard set of arguments used during
|
||||||
cross-compilation. Additional parameters can be passed to
|
cross-compilation. Additional parameters can be passed to
|
||||||
<command>configure</command> through the <glossterm><link
|
<command>configure</command> through the <glossterm><link
|
||||||
|
|
|
@ -40,10 +40,10 @@
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
This directory contains user configuration files and the output
|
This directory contains user configuration files and the output
|
||||||
from Poky. It's now deprecated to be a sub-directory in Poky source tree,
|
generated by Poky in its standard configuration where the source tree is
|
||||||
though it's still supported. The desired way is to use <link
|
combined with the output. It is also possible to place output and configuration
|
||||||
linkend='structure-core-script'>seperate output directory</link> for build
|
files in a directory separate from the Poky source, see the section <link
|
||||||
outside of Poky source tree.
|
linkend='structure-core-script'>seperate output directory</link>.
|
||||||
</para>
|
</para>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
|
@ -136,7 +136,7 @@
|
||||||
a shell makes changes to PATH and sets other core BitBake variables based on the
|
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.
|
current working directory. You need to use this before running Poky commands.
|
||||||
Internally it uses scripts within the <filename class="directory">scripts/
|
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:
|
specifying any directory as the build output:
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
@ -145,9 +145,9 @@ source POKY_SRC/poky-init-build-env [BUILDDIR]
|
||||||
</programlisting>
|
</programlisting>
|
||||||
|
|
||||||
<para>
|
<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
|
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>
|
</para>
|
||||||
</section>
|
</section>
|
||||||
</section>
|
</section>
|
||||||
|
@ -182,7 +182,7 @@ source POKY_SRC/poky-init-build-env [BUILDDIR]
|
||||||
<para>
|
<para>
|
||||||
This file defines layers walked by bitbake. If there's no <filename>
|
This file defines layers walked by bitbake. If there's no <filename>
|
||||||
bblayers.conf</filename> present, it is created from <filename>bblayers.conf.sample
|
bblayers.conf</filename> present, it is created from <filename>bblayers.conf.sample
|
||||||
</filename>.
|
</filename> when the environment setup script is sourced.
|
||||||
</para>
|
</para>
|
||||||
</section>
|
</section>
|
||||||
|
|
||||||
|
|
|
@ -109,7 +109,7 @@
|
||||||
<para>A regular expression which evalutates to match the machines the recipe
|
<para>A regular expression which evalutates to match the machines the recipe
|
||||||
works with. It stops recipes being run on machines they're incompatible with,
|
works with. It stops recipes being run on machines they're incompatible with,
|
||||||
which is partciuarly useful with kernels. It also helps to increase parsing
|
which is partciuarly useful with kernels. It also helps to increase parsing
|
||||||
speed that, further parsing of the recipe is skipped as if it found the current
|
speed as further parsing of the recipe is skipped as if it found the current
|
||||||
machine is not compatible.</para>
|
machine is not compatible.</para>
|
||||||
</glossdef>
|
</glossdef>
|
||||||
</glossentry>
|
</glossentry>
|
||||||
|
|
Loading…
Reference in New Issue