From 825366d7f0094e64799cd5fc5223b29a0db2b648 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Fri, 24 Jan 2014 09:50:29 -0600 Subject: [PATCH] bitbake: user-manual-ref-variables.xml: Added 6 new variables to glossary: MULTI_PROVIDER_WHITELIST CACHE PERSISTENT_DIR FETCHCMD FILE FILESDIR (Bitbake rev: 4aa8c2f93cc126778f7e99229d99b398d603fcac) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- .../user-manual/user-manual-ref-variables.xml | 95 ++++++++++++++++++- 1 file changed, 92 insertions(+), 3 deletions(-) diff --git a/bitbake/doc/user-manual/user-manual-ref-variables.xml b/bitbake/doc/user-manual/user-manual-ref-variables.xml index 9cf42fd0a4..05fbd5df87 100644 --- a/bitbake/doc/user-manual/user-manual-ref-variables.xml +++ b/bitbake/doc/user-manual/user-manual-ref-variables.xml @@ -17,7 +17,7 @@ A B - + C D E F @@ -930,10 +930,19 @@ - D @@ -1118,6 +1127,48 @@ + FETCHCMD + + + Defines the command the BitBake fetcher module + executes when running fetch operations. + You need to use an override suffix when you use the + variable (e.g. FETCHCMD_git + or FETCHCMD_svn). + + + + + FILE + + + Points at the current file. + BitBake sets this variable during the parsing process + to identify the file being parsed. + BitBake also sets this variable when a recipe is being + executed to identify the recipe file. + + + + + FILESDIR + + + Specifies directories BitBake uses when searching for + patches and files. + The "local" fetcher module uses these directories when + handling file:// URLs if the file + was not found using + FILESPATH. + + The FILESDIR variable is + deprecated and you should use + FILESPATH in all new code. + + + + + FILESPATH @@ -1248,6 +1299,32 @@ + MULTI_PROVIDER_WHITELIST + + + Allows you to suppress BitBake warnings caused when + building two separate recipes that provide the same + output. + + + + Bitbake normally issues a warning when building two + different recipes where each provides the same output. + This scenario is usually something the user does not + want. + However, cases do exist where it makes sense, particularly + in the virtual/* namespace. + You can use this variable to suppress BitBake's warnings. + + + + To use the variable, list provider names (e.g. + recipe names, virtual/kernel, + and so forth). + + + +