sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

Poky Reference Manual: XML tag clean up and command example text indentation. 

Removed a couple of redundant </ulink> tags.
Also indented the literallayout text by five spaces for formatting.

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
This commit is contained in:
Scott Rifenbark 2010-11-09 13:14:00 -08:00 committed by Richard Purdie
parent d16bbc076a
commit 00b5b4dff7
1 changed files with 17 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

31
documentation/poky-ref-manual/usingpoky.xml
View File

@ -66,7 +66,7 @@
Bitbake chooses the one selected by the distribution configuration. Bitbake chooses the one selected by the distribution configuration.
You can get more details about how bitbake chooses between different versions You can get more details about how bitbake chooses between different versions
and providers in the <link linkend='ref-bitbake-providers'> and providers in the <link linkend='ref-bitbake-providers'>
'Preferences and Providers' section</link>. 'Preferences and Providers'</link> section.
</para> </para>
<para> <para>
Bitbake also tries to execute any dependent tasks first. Bitbake also tries to execute any dependent tasks first.
@ -131,8 +131,8 @@
</para> </para>
<para> <para>
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ source poky-init-build-env [build_dir] $ source poky-init-build-env [build_dir]
</literallayout> </literallayout>
</para> </para>
<para> <para>
The build_dir is the dir containing all the build's object files. The default The build_dir is the dir containing all the build's object files. The default
@ -146,8 +146,8 @@ $ source poky-init-build-env [build_dir]
</para> </para>
<para> <para>
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ bitbake &lt;target&gt; $ bitbake &lt;target&gt;
</literallayout> </literallayout>
</para> </para>
<para> <para>
The target is the name of the recipe you want to build. The target is the name of the recipe you want to build.
@ -169,7 +169,7 @@ $ bitbake &lt;target&gt;
<filename class="directory">tmp/deploy/images</filename> directory. <filename class="directory">tmp/deploy/images</filename> directory.
Running qemux86 and qemuarm images is described in the Running qemux86 and qemuarm images is described in the
'Using Pre-Built Binaries and QEMU' section of the Yocto Project Quick Start. 'Using Pre-Built Binaries and QEMU' section of the Yocto Project Quick Start.
See <ulink url="http://www.yoctoproject.org//docs/yocto-quick-start/yocto-project-qs.html"></ulink> See <ulink url="http://www.yoctoproject.org//docs/yocto-quick-start/yocto-project-qs.html"/>
for the guide. for the guide.
For information about how to install these images, see the documentation for your For information about how to install these images, see the documentation for your
particular board/machine. particular board/machine.
@ -201,13 +201,16 @@ $ bitbake &lt;target&gt;
<filename>run.do_taskname.pid </filename> file located in the same directory. <filename>run.do_taskname.pid </filename> file located in the same directory.
</para> </para>
<para>Presently, the output from python tasks is sent directly to the console.</para> <para>
Presently, the output from python tasks is sent directly to the console.
</para>
</section> </section>
<section id='usingpoky-debugging-taskrunning'> <section id='usingpoky-debugging-taskrunning'>
<title>Running Specific Tasks</title> <title>Running Specific Tasks</title>
<para> Any given package consists of a set of tasks. <para>
Any given package consists of a set of tasks.
In most cases the series is: fetch, unpack, patch, configure, In most cases the series is: fetch, unpack, patch, configure,
compile, install, package, package_write and build. compile, install, package, package_write and build.
The default task is "build" and any tasks on which it depends build first - hence, The default task is "build" and any tasks on which it depends build first - hence,
@ -216,7 +219,7 @@ $ bitbake &lt;target&gt;
If you wish to run a task that is not part of the default build chain you can use the If you wish to run a task that is not part of the default build chain you can use the
"-c" option in bitbake as follows: "-c" option in bitbake as follows:
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ bitbake matchbox-desktop -c devshell $ bitbake matchbox-desktop -c devshell
</literallayout> </literallayout>
</para> </para>
@ -228,10 +231,10 @@ $ bitbake matchbox-desktop -c devshell
<para> <para>
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ bitbake matchbox-desktop $ bitbake matchbox-desktop
[make some changes to the source code in the WORKDIR] [make some changes to the source code in the WORKDIR]
$ bitbake matchbox-desktop -c compile -f $ bitbake matchbox-desktop -c compile -f
$ bitbake matchbox-desktop $ bitbake matchbox-desktop
</literallayout> </literallayout>
</para> </para>
@ -246,7 +249,7 @@ $ bitbake matchbox-desktop
You can view a list of tasks in a given package by running the listtasks task. You can view a list of tasks in a given package by running the listtasks task.
For example: For example:
<literallayout class='monospaced'> <literallayout class='monospaced'>
$ bitbake matchbox-desktop -c $ bitbake matchbox-desktop -c
</literallayout> </literallayout>
The results are in the file <filename>${WORKDIR}/temp/log.do_listtasks</filename>. The results are in the file <filename>${WORKDIR}/temp/log.do_listtasks</filename>.
</para> </para>