diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2013-11-06 08:55:06 -0800 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2013-12-03 12:53:04 +0000 |
commit | 4a5282213f00bc7361ee69930426debda1e83584 (patch) | |
tree | a5a6ece67b0f7d49ec34a5c3e3adab95ee303cbb /documentation/ref-manual/usingpoky.xml | |
parent | f16706d936bf1842448b64029581ed214069a94c (diff) | |
download | poky-4a5282213f00bc7361ee69930426debda1e83584.tar.gz |
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: ab352523e82626d8356d8b2c07fb10d2d60ea254)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/usingpoky.xml')
-rw-r--r-- | documentation/ref-manual/usingpoky.xml | 33 |
1 files changed, 22 insertions, 11 deletions
diff --git a/documentation/ref-manual/usingpoky.xml b/documentation/ref-manual/usingpoky.xml index 1edc9ea238..49166e15bf 100644 --- a/documentation/ref-manual/usingpoky.xml +++ b/documentation/ref-manual/usingpoky.xml | |||
@@ -271,12 +271,18 @@ | |||
271 | <section id='usingpoky-debugging-buildfile'> | 271 | <section id='usingpoky-debugging-buildfile'> |
272 | <title>Building with No Dependencies</title> | 272 | <title>Building with No Dependencies</title> |
273 | <para> | 273 | <para> |
274 | If you really want to build a specific <filename>.bb</filename> file, you can use | 274 | To build a specific recipe (<filename>.bb</filename> file), |
275 | the command form <filename>bitbake -b <somepath/somefile.bb></filename>. | 275 | you can use the following command form: |
276 | This command form does not check for dependencies so you should use it | 276 | <literallayout class='monospaced'> |
277 | only when you know its dependencies already exist. | 277 | $ bitbake -b <somepath/somerecipe.bb> |
278 | You can also specify fragments of the filename. | 278 | </literallayout> |
279 | In this case, BitBake checks for a unique match. | 279 | This command form does not check for dependencies. |
280 | Consequently, you should use it | ||
281 | only when you know dependencies already exist. | ||
282 | <note> | ||
283 | You can also specify fragments of the filename. | ||
284 | In this case, BitBake checks for a unique match. | ||
285 | </note> | ||
280 | </para> | 286 | </para> |
281 | </section> | 287 | </section> |
282 | 288 | ||
@@ -284,11 +290,16 @@ | |||
284 | <title>Variables</title> | 290 | <title>Variables</title> |
285 | <para> | 291 | <para> |
286 | You can use the <filename>-e</filename> BitBake option to | 292 | You can use the <filename>-e</filename> BitBake option to |
287 | display the resulting environment for a configuration | 293 | display the parsing environment for a configuration. |
288 | when you do not specify a package or for a specific package when | 294 | The following displays the general parsing environment: |
289 | you do specify the package. | 295 | <literallayout class='monospaced'> |
290 | If you want to show the environment resulting from parsing a single | 296 | $ bitbake -e |
291 | recipe, use the <filename>-b recipename</filename> form. | 297 | </literallayout> |
298 | This next example shows the parsing environment for a specific | ||
299 | recipe: | ||
300 | <literallayout class='monospaced'> | ||
301 | $ bitbake -e <recipename> | ||
302 | </literallayout> | ||
292 | </para> | 303 | </para> |
293 | </section> | 304 | </section> |
294 | 305 | ||