From bf77e55a5ec1cb111579cbd61e2af0621b0861e4 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Wed, 6 Nov 2013 08:55:06 -0800 Subject: [PATCH] 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 Signed-off-by: Richard Purdie --- documentation/ref-manual/usingpoky.xml | 33 +++++++++++++++++--------- 1 file 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 @@
Building with No Dependencies - If you really want to build a specific .bb file, you can use - the command form bitbake -b <somepath/somefile.bb>. - 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 (.bb file), + you can use the following command form: + + $ bitbake -b <somepath/somerecipe.bb> + + This command form does not check for dependencies. + Consequently, you should use it + only when you know dependencies already exist. + + You can also specify fragments of the filename. + In this case, BitBake checks for a unique match. +
@@ -284,11 +290,16 @@ Variables You can use the -e 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 -b recipename form. + display the parsing environment for a configuration. + The following displays the general parsing environment: + + $ bitbake -e + + This next example shows the parsing environment for a specific + recipe: + + $ bitbake -e <recipename> +