diff options
author | Scott Rifenbark <scott.m.rifenbark@intel.com> | 2012-02-28 12:21:35 -0600 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2012-03-08 12:08:04 -0800 |
commit | 05cff8adcb22b43fa8135a37af4799cd00a8d11b (patch) | |
tree | 9f6dfa1151eeb76e205e10a2dc4fb67aebf11d9f /documentation | |
parent | 36e3daf7f924fbf15ab9c1764c424046adffff5e (diff) | |
download | poky-05cff8adcb22b43fa8135a37af4799cd00a8d11b.tar.gz |
documentation/poky-ref-manual/ref-variables.xml: B and BBCLASSEXTEND
Added two new variable entries. This is part of the fix needed
as a result of the feedback from two Community members inside
Intel whose feedback was initially reported by Darren Hart.
Reported-by: Inaky Perez-Gonzales <inaky.perez-gonzales@intel.com>
Reported-by: Mohamed Abbas <mohamed.abbas@intel.com>
(From yocto-docs rev: ccabb9c905e7a1c9a211f805f8a326048903b7b0)
Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-rw-r--r-- | documentation/poky-ref-manual/ref-variables.xml | 50 |
1 files changed, 47 insertions, 3 deletions
diff --git a/documentation/poky-ref-manual/ref-variables.xml b/documentation/poky-ref-manual/ref-variables.xml index 1e31e0a3ab..ec747bf5f9 100644 --- a/documentation/poky-ref-manual/ref-variables.xml +++ b/documentation/poky-ref-manual/ref-variables.xml | |||
@@ -16,7 +16,7 @@ | |||
16 | 16 | ||
17 | <para> | 17 | <para> |
18 | <link linkend='var-AUTHOR'>A</link> | 18 | <link linkend='var-AUTHOR'>A</link> |
19 | <link linkend='var-BAD_RECOMMENDATIONS'>B</link> | 19 | <link linkend='var-B'>B</link> |
20 | <link linkend='var-CFLAGS'>C</link> | 20 | <link linkend='var-CFLAGS'>C</link> |
21 | <link linkend='var-D'>D</link> | 21 | <link linkend='var-D'>D</link> |
22 | <link linkend='var-ENABLE_BINARY_LOCALE_GENERATION'>E</link> | 22 | <link linkend='var-ENABLE_BINARY_LOCALE_GENERATION'>E</link> |
@@ -64,14 +64,58 @@ | |||
64 | 64 | ||
65 | <glossdiv id='var-glossary-b'><title>B</title> | 65 | <glossdiv id='var-glossary-b'><title>B</title> |
66 | 66 | ||
67 | <glossentry id='var-B'><glossterm>B</glossterm> | ||
68 | <glossdef> | ||
69 | <para> | ||
70 | The directory in which the Yocto Project build system places | ||
71 | generated objects during a recipe's build process. | ||
72 | By default, this directory is the same as the <link linkend='var-S'><filename>S</filename></link> | ||
73 | directory: | ||
74 | <literallayout class='monospaced'> | ||
75 | B = ${WORKDIR}/${BPN}-{PV}/ | ||
76 | </literallayout> | ||
77 | You can separate the source directory (<filename>S</filename>) and the directory pointed to | ||
78 | by the <filename>B</filename> variable. | ||
79 | In general, <filename>autotools</filename>, recipes such as <filename>gcc</filename>, | ||
80 | and some kernel recipes separate these directories by default. | ||
81 | </para> | ||
82 | </glossdef> | ||
83 | </glossentry> | ||
84 | |||
67 | <glossentry id='var-BAD_RECOMMENDATIONS'><glossterm>BAD_RECOMMENDATIONS</glossterm> | 85 | <glossentry id='var-BAD_RECOMMENDATIONS'><glossterm>BAD_RECOMMENDATIONS</glossterm> |
68 | <glossdef> | 86 | <glossdef> |
69 | <para>A list of packages not to install despite being recommended by a recipe. | 87 | <para> |
88 | A list of packages not to install despite being recommended by a recipe. | ||
70 | Support for this variable exists only for images that use the | 89 | Support for this variable exists only for images that use the |
71 | <filename>ipkg</filename> packaging system.</para> | 90 | <filename>ipkg</filename> packaging system. |
91 | </para> | ||
72 | </glossdef> | 92 | </glossdef> |
73 | </glossentry> | 93 | </glossentry> |
74 | 94 | ||
95 | <glossentry id='var-BBCLASSEXTEND'><glossterm>BBCLASSEXTEND</glossterm> | ||
96 | <glossdef> | ||
97 | <para> | ||
98 | Allows you to extend a recipe so that it builds variants of the software. | ||
99 | Common variants for recipes exist such as "natives" like <filename>quilt-native</filename>, | ||
100 | which is a copy of quilt built to run on the build system; | ||
101 | "crosses" such as <filename>gcc-cross</filename>, | ||
102 | which is a compiler built to run on the build machine but produces binaries | ||
103 | that run on the target <link linkend='var-MACHINE'><filename>MACHINE</filename></link>; | ||
104 | "nativesdk", which targets the SDK machine instead of <filename>MACHINE</filename>; | ||
105 | and "mulitlibs" in the form "<filename>multilib:<multilib_name></filename>". | ||
106 | </para> | ||
107 | |||
108 | <para> | ||
109 | To build a different variant of the recipe with a minimal amount of code, it usually | ||
110 | is as simple as adding the following to your recipe: | ||
111 | <literallayout class='monospaced'> | ||
112 | BBCLASSEXTEND = "native nativesdk" | ||
113 | BBCLASSEXTEND = "multilib:<multilib_name>" | ||
114 | </literallayout> | ||
115 | </para> | ||
116 | </glossdef> | ||
117 | </glossentry> | ||
118 | |||
75 | <glossentry id='var-BBMASK'><glossterm>BBMASK</glossterm> | 119 | <glossentry id='var-BBMASK'><glossterm>BBMASK</glossterm> |
76 | <glossdef> | 120 | <glossdef> |
77 | <para>Prevents BitBake from processing recipes and recipe append files. | 121 | <para>Prevents BitBake from processing recipes and recipe append files. |