summaryrefslogtreecommitdiffstats
path: root/bitbake/doc/bitbake-user-manual
diff options
context:
space:
mode:
authorRobert P. J. Day <rpjday@crashcourse.ca>2020-02-07 04:37:59 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2020-02-08 17:41:17 +0000
commit94208e7bf4b700dd71b7d528f604af5944126c0d (patch)
tree578c45aebb8f5bd6599baddb1af5392f8cf3032d /bitbake/doc/bitbake-user-manual
parent9f6a310002ad557a27b442322e91bc25bf096cb3 (diff)
downloadpoky-94208e7bf4b700dd71b7d528f604af5944126c0d.tar.gz
bitbake: doc: Standardize spelling on 'BitBake' throughout docs
Since the proper spelling is, in fact, 'BitBake', might as well make it consistent throughout the user manual. (Bitbake rev: 79ada807de0b202c3d568fc4365a1d3f17ba1bce) Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/doc/bitbake-user-manual')
-rw-r--r--bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml8
-rw-r--r--bitbake/doc/bitbake-user-manual/bitbake-user-manual-fetching.xml2
-rw-r--r--bitbake/doc/bitbake-user-manual/bitbake-user-manual-hello.xml14
-rw-r--r--bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml2
-rw-r--r--bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml8
-rw-r--r--bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml2
6 files changed, 18 insertions, 18 deletions
diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml
index 46dafeee30..8f606676b4 100644
--- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml
+++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml
@@ -113,7 +113,7 @@
113 </para> 113 </para>
114 114
115 <para> 115 <para>
116 Prior to parsing configuration files, Bitbake looks 116 Prior to parsing configuration files, BitBake looks
117 at certain variables, including: 117 at certain variables, including:
118 <itemizedlist> 118 <itemizedlist>
119 <listitem><para> 119 <listitem><para>
@@ -339,7 +339,7 @@
339 <link linkend='var-bb-BB_HASHCONFIG_WHITELIST'><filename>BB_HASHCONFIG_WHITELIST</filename></link>) 339 <link linkend='var-bb-BB_HASHCONFIG_WHITELIST'><filename>BB_HASHCONFIG_WHITELIST</filename></link>)
340 and then checking if the checksum matches. 340 and then checking if the checksum matches.
341 If that checksum matches what is in the cache and the recipe 341 If that checksum matches what is in the cache and the recipe
342 and class files have not changed, Bitbake is able to use 342 and class files have not changed, BitBake is able to use
343 the cache. 343 the cache.
344 BitBake then reloads the cached information about the recipe 344 BitBake then reloads the cached information about the recipe
345 instead of reparsing it from scratch. 345 instead of reparsing it from scratch.
@@ -429,7 +429,7 @@
429 The default 429 The default
430 <link linkend='var-bb-PREFERRED_PROVIDER'><filename>PREFERRED_PROVIDER</filename></link> 430 <link linkend='var-bb-PREFERRED_PROVIDER'><filename>PREFERRED_PROVIDER</filename></link>
431 is the provider with the same name as the target. 431 is the provider with the same name as the target.
432 Bitbake iterates through each target it needs to build and 432 BitBake iterates through each target it needs to build and
433 resolves them and their dependencies using this process. 433 resolves them and their dependencies using this process.
434 </para> 434 </para>
435 435
@@ -821,7 +821,7 @@
821 821
822 <para> 822 <para>
823 It is worth noting that BitBake's "-S" option lets you 823 It is worth noting that BitBake's "-S" option lets you
824 debug Bitbake's processing of signatures. 824 debug BitBake's processing of signatures.
825 The options passed to -S allow different debugging modes 825 The options passed to -S allow different debugging modes
826 to be used, either using BitBake's own debug functions 826 to be used, either using BitBake's own debug functions
827 or possibly those defined in the metadata/signature handler 827 or possibly those defined in the metadata/signature handler
diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-fetching.xml b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-fetching.xml
index 684040856d..d1bfc23362 100644
--- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-fetching.xml
+++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-fetching.xml
@@ -139,7 +139,7 @@
139 </para> 139 </para>
140 140
141 <para> 141 <para>
142 Since network accesses are slow, Bitbake maintains a 142 Since network accesses are slow, BitBake maintains a
143 cache of files downloaded from the network. 143 cache of files downloaded from the network.
144 Any source files that are not local (i.e. 144 Any source files that are not local (i.e.
145 downloaded from the Internet) are placed into the download 145 downloaded from the Internet) are placed into the download
diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-hello.xml b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-hello.xml
index 39066e4b15..11eb36aaf8 100644
--- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-hello.xml
+++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-hello.xml
@@ -166,7 +166,7 @@
166 Having a project directory is a good way to isolate your 166 Having a project directory is a good way to isolate your
167 project. 167 project.
168 </para></listitem> 168 </para></listitem>
169 <listitem><para><emphasis>Run Bitbake:</emphasis> 169 <listitem><para><emphasis>Run BitBake:</emphasis>
170 At this point, you have nothing but a project directory. 170 At this point, you have nothing but a project directory.
171 Run the <filename>bitbake</filename> command and see what 171 Run the <filename>bitbake</filename> command and see what
172 it does: 172 it does:
@@ -197,7 +197,7 @@
197 <link linkend='var-bb-BBPATH'><filename>BBPATH</filename></link> 197 <link linkend='var-bb-BBPATH'><filename>BBPATH</filename></link>
198 variable is what tells BitBake where to look for those files. 198 variable is what tells BitBake where to look for those files.
199 <filename>BBPATH</filename> is not set and you need to set it. 199 <filename>BBPATH</filename> is not set and you need to set it.
200 Without <filename>BBPATH</filename>, Bitbake cannot 200 Without <filename>BBPATH</filename>, BitBake cannot
201 find any configuration files (<filename>.conf</filename>) 201 find any configuration files (<filename>.conf</filename>)
202 or recipe files (<filename>.bb</filename>) at all. 202 or recipe files (<filename>.bb</filename>) at all.
203 BitBake also cannot find the <filename>bitbake.conf</filename> 203 BitBake also cannot find the <filename>bitbake.conf</filename>
@@ -225,7 +225,7 @@
225 as the shell would. 225 as the shell would.
226 </note> 226 </note>
227 </para></listitem> 227 </para></listitem>
228 <listitem><para><emphasis>Run Bitbake:</emphasis> 228 <listitem><para><emphasis>Run BitBake:</emphasis>
229 Now that you have <filename>BBPATH</filename> defined, run 229 Now that you have <filename>BBPATH</filename> defined, run
230 the <filename>bitbake</filename> command again: 230 the <filename>bitbake</filename> command again:
231 <literallayout class='monospaced'> 231 <literallayout class='monospaced'>
@@ -313,7 +313,7 @@
313 example, click on the links to take you to the definitions in 313 example, click on the links to take you to the definitions in
314 the glossary. 314 the glossary.
315 </para></listitem> 315 </para></listitem>
316 <listitem><para><emphasis>Run Bitbake:</emphasis> 316 <listitem><para><emphasis>Run BitBake:</emphasis>
317 After making sure that the <filename>conf/bitbake.conf</filename> 317 After making sure that the <filename>conf/bitbake.conf</filename>
318 file exists, you can run the <filename>bitbake</filename> 318 file exists, you can run the <filename>bitbake</filename>
319 command again: 319 command again:
@@ -364,7 +364,7 @@
364 more depending on which build environments BitBake is 364 more depending on which build environments BitBake is
365 supporting. 365 supporting.
366 </para></listitem> 366 </para></listitem>
367 <listitem><para><emphasis>Run Bitbake:</emphasis> 367 <listitem><para><emphasis>Run BitBake:</emphasis>
368 After making sure that the <filename>classes/base.bbclass</filename> 368 After making sure that the <filename>classes/base.bbclass</filename>
369 file exists, you can run the <filename>bitbake</filename> 369 file exists, you can run the <filename>bitbake</filename>
370 command again: 370 command again:
@@ -434,7 +434,7 @@
434 For more information on these variables, follow the links 434 For more information on these variables, follow the links
435 to the glossary. 435 to the glossary.
436 </para></listitem> 436 </para></listitem>
437 <listitem><para><emphasis>Run Bitbake With a Target:</emphasis> 437 <listitem><para><emphasis>Run BitBake With a Target:</emphasis>
438 Now that a BitBake target exists, run the command and provide 438 Now that a BitBake target exists, run the command and provide
439 that target: 439 that target:
440 <literallayout class='monospaced'> 440 <literallayout class='monospaced'>
@@ -468,7 +468,7 @@
468 You need to provide your own information for 468 You need to provide your own information for
469 <filename>you</filename> in the file. 469 <filename>you</filename> in the file.
470 </para></listitem> 470 </para></listitem>
471 <listitem><para><emphasis>Run Bitbake With a Target:</emphasis> 471 <listitem><para><emphasis>Run BitBake With a Target:</emphasis>
472 Now that you have supplied the <filename>bblayers.conf</filename> 472 Now that you have supplied the <filename>bblayers.conf</filename>
473 file, run the <filename>bitbake</filename> command and provide 473 file, run the <filename>bitbake</filename> command and provide
474 the target: 474 the target:
diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml
index 8f2a960cac..c87eac5242 100644
--- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml
+++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml
@@ -448,7 +448,7 @@
448 <listitem><para><emphasis>Using the BitBake that Comes With Your 448 <listitem><para><emphasis>Using the BitBake that Comes With Your
449 Build Checkout:</emphasis> 449 Build Checkout:</emphasis>
450 A final possibility for getting a copy of BitBake is that it 450 A final possibility for getting a copy of BitBake is that it
451 already comes with your checkout of a larger Bitbake-based build 451 already comes with your checkout of a larger BitBake-based build
452 system, such as Poky. 452 system, such as Poky.
453 Rather than manually checking out individual layers and 453 Rather than manually checking out individual layers and
454 gluing them together yourself, you can check 454 gluing them together yourself, you can check
diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
index 421364c2cf..383f94b162 100644
--- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
+++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-metadata.xml
@@ -5,7 +5,7 @@
5 <title>Syntax and Operators</title> 5 <title>Syntax and Operators</title>
6 6
7 <para> 7 <para>
8 Bitbake files have their own syntax. 8 BitBake files have their own syntax.
9 The syntax has similarities to several 9 The syntax has similarities to several
10 other languages but also has some unique features. 10 other languages but also has some unique features.
11 This section describes the available syntax and operators 11 This section describes the available syntax and operators
@@ -1414,7 +1414,7 @@
1414 </section> 1414 </section>
1415 1415
1416 <section id='bitbake-style-python-functions-versus-python-functions'> 1416 <section id='bitbake-style-python-functions-versus-python-functions'>
1417 <title>Bitbake-Style Python Functions Versus Python Functions</title> 1417 <title>BitBake-Style Python Functions Versus Python Functions</title>
1418 1418
1419 <para> 1419 <para>
1420 Following are some important differences between 1420 Following are some important differences between
@@ -1895,7 +1895,7 @@
1895 <para> 1895 <para>
1896 Sometimes, it is useful to be able to obtain information 1896 Sometimes, it is useful to be able to obtain information
1897 from the original execution environment. 1897 from the original execution environment.
1898 Bitbake saves a copy of the original environment into 1898 BitBake saves a copy of the original environment into
1899 a special variable named 1899 a special variable named
1900 <link linkend='var-bb-BB_ORIGENV'><filename>BB_ORIGENV</filename></link>. 1900 <link linkend='var-bb-BB_ORIGENV'><filename>BB_ORIGENV</filename></link>.
1901 </para> 1901 </para>
@@ -2616,7 +2616,7 @@
2616 <para> 2616 <para>
2617 It is often necessary to access variables in the 2617 It is often necessary to access variables in the
2618 BitBake datastore using Python functions. 2618 BitBake datastore using Python functions.
2619 The Bitbake datastore has an API that allows you this 2619 The BitBake datastore has an API that allows you this
2620 access. 2620 access.
2621 Here is a list of available operations: 2621 Here is a list of available operations:
2622 </para> 2622 </para>
diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml
index aca6741c21..bae01d90c0 100644
--- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml
+++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml
@@ -1780,7 +1780,7 @@
1780 </para> 1780 </para>
1781 1781
1782 <para> 1782 <para>
1783 Bitbake normally issues a warning when building two 1783 BitBake normally issues a warning when building two
1784 different recipes where each provides the same output. 1784 different recipes where each provides the same output.
1785 This scenario is usually something the user does not 1785 This scenario is usually something the user does not
1786 want. 1786 want.