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

ref-manual: Updates to "Variables" and "Building with No Dependencies" 

There was some confusion over some things in these two sections.
I re-wrote them with the help of Paul Eggleton to be clear on
them.

Reported-by: Robert P. J. Day (rpjday@crashcourse.ca>
(From yocto-docs rev: 076aa5d8244ed3fcf321ef61da5d2270b40a7791)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2013-11-06 08:55:06 -08:00 committed by Richard Purdie
parent 0d9874d9a3
commit bf77e55a5e
1 changed files with 22 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

33
documentation/ref-manual/usingpoky.xml
View File

@ -271,12 +271,18 @@
<section id='usingpoky-debugging-buildfile'>
<title>Building with No Dependencies</title>
<para>
If you really want to build a specific <filename>.bb</filename> file, you can use
the command form <filename>bitbake -b &lt;somepath/somefile.bb&gt;</filename>.
This command form does not check for dependencies so you should use it
only when you know its dependencies already exist.
You can also specify fragments of the filename.
In this case, BitBake checks for a unique match.
To build a specific recipe (<filename>.bb</filename> file),
you can use the following command form:
<literallayout class='monospaced'>
$ bitbake -b &lt;somepath/somerecipe.bb&gt;
</literallayout>
This command form does not check for dependencies.
Consequently, you should use it
only when you know dependencies already exist.
<note>
You can also specify fragments of the filename.
In this case, BitBake checks for a unique match.
</note>
</para>
</section>
@ -284,11 +290,16 @@
<title>Variables</title>
<para>
You can use the <filename>-e</filename> BitBake option to
display the resulting environment for a configuration
when you do not specify a package or for a specific package when
you do specify the package.
If you want to show the environment resulting from parsing a single
recipe, use the <filename>-b recipename</filename> form.
display the parsing environment for a configuration.
The following displays the general parsing environment:
<literallayout class='monospaced'>
$ bitbake -e
</literallayout>
This next example shows the parsing environment for a specific
recipe:
<literallayout class='monospaced'>
$ bitbake -e &lt;recipename&gt;
</literallayout>
</para>
</section>