mirror of
https://git.yoctoproject.org/poky
synced 2026-09-19 18:49:32 +02:00
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>
This commit is contained in:
committed by
Richard Purdie
parent
9f6a310002
commit
94208e7bf4
@@ -113,7 +113,7 @@
|
|||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Prior to parsing configuration files, Bitbake looks
|
Prior to parsing configuration files, BitBake looks
|
||||||
at certain variables, including:
|
at certain variables, including:
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
<listitem><para>
|
<listitem><para>
|
||||||
@@ -339,7 +339,7 @@
|
|||||||
<link linkend='var-bb-BB_HASHCONFIG_WHITELIST'><filename>BB_HASHCONFIG_WHITELIST</filename></link>)
|
<link linkend='var-bb-BB_HASHCONFIG_WHITELIST'><filename>BB_HASHCONFIG_WHITELIST</filename></link>)
|
||||||
and then checking if the checksum matches.
|
and then checking if the checksum matches.
|
||||||
If that checksum matches what is in the cache and the recipe
|
If that checksum matches what is in the cache and the recipe
|
||||||
and class files have not changed, Bitbake is able to use
|
and class files have not changed, BitBake is able to use
|
||||||
the cache.
|
the cache.
|
||||||
BitBake then reloads the cached information about the recipe
|
BitBake then reloads the cached information about the recipe
|
||||||
instead of reparsing it from scratch.
|
instead of reparsing it from scratch.
|
||||||
@@ -429,7 +429,7 @@
|
|||||||
The default
|
The default
|
||||||
<link linkend='var-bb-PREFERRED_PROVIDER'><filename>PREFERRED_PROVIDER</filename></link>
|
<link linkend='var-bb-PREFERRED_PROVIDER'><filename>PREFERRED_PROVIDER</filename></link>
|
||||||
is the provider with the same name as the target.
|
is the provider with the same name as the target.
|
||||||
Bitbake iterates through each target it needs to build and
|
BitBake iterates through each target it needs to build and
|
||||||
resolves them and their dependencies using this process.
|
resolves them and their dependencies using this process.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
@@ -821,7 +821,7 @@
|
|||||||
|
|
||||||
<para>
|
<para>
|
||||||
It is worth noting that BitBake's "-S" option lets you
|
It is worth noting that BitBake's "-S" option lets you
|
||||||
debug Bitbake's processing of signatures.
|
debug BitBake's processing of signatures.
|
||||||
The options passed to -S allow different debugging modes
|
The options passed to -S allow different debugging modes
|
||||||
to be used, either using BitBake's own debug functions
|
to be used, either using BitBake's own debug functions
|
||||||
or possibly those defined in the metadata/signature handler
|
or possibly those defined in the metadata/signature handler
|
||||||
|
|||||||
@@ -139,7 +139,7 @@
|
|||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Since network accesses are slow, Bitbake maintains a
|
Since network accesses are slow, BitBake maintains a
|
||||||
cache of files downloaded from the network.
|
cache of files downloaded from the network.
|
||||||
Any source files that are not local (i.e.
|
Any source files that are not local (i.e.
|
||||||
downloaded from the Internet) are placed into the download
|
downloaded from the Internet) are placed into the download
|
||||||
|
|||||||
@@ -166,7 +166,7 @@
|
|||||||
Having a project directory is a good way to isolate your
|
Having a project directory is a good way to isolate your
|
||||||
project.
|
project.
|
||||||
</para></listitem>
|
</para></listitem>
|
||||||
<listitem><para><emphasis>Run Bitbake:</emphasis>
|
<listitem><para><emphasis>Run BitBake:</emphasis>
|
||||||
At this point, you have nothing but a project directory.
|
At this point, you have nothing but a project directory.
|
||||||
Run the <filename>bitbake</filename> command and see what
|
Run the <filename>bitbake</filename> command and see what
|
||||||
it does:
|
it does:
|
||||||
@@ -197,7 +197,7 @@
|
|||||||
<link linkend='var-bb-BBPATH'><filename>BBPATH</filename></link>
|
<link linkend='var-bb-BBPATH'><filename>BBPATH</filename></link>
|
||||||
variable is what tells BitBake where to look for those files.
|
variable is what tells BitBake where to look for those files.
|
||||||
<filename>BBPATH</filename> is not set and you need to set it.
|
<filename>BBPATH</filename> is not set and you need to set it.
|
||||||
Without <filename>BBPATH</filename>, Bitbake cannot
|
Without <filename>BBPATH</filename>, BitBake cannot
|
||||||
find any configuration files (<filename>.conf</filename>)
|
find any configuration files (<filename>.conf</filename>)
|
||||||
or recipe files (<filename>.bb</filename>) at all.
|
or recipe files (<filename>.bb</filename>) at all.
|
||||||
BitBake also cannot find the <filename>bitbake.conf</filename>
|
BitBake also cannot find the <filename>bitbake.conf</filename>
|
||||||
@@ -225,7 +225,7 @@
|
|||||||
as the shell would.
|
as the shell would.
|
||||||
</note>
|
</note>
|
||||||
</para></listitem>
|
</para></listitem>
|
||||||
<listitem><para><emphasis>Run Bitbake:</emphasis>
|
<listitem><para><emphasis>Run BitBake:</emphasis>
|
||||||
Now that you have <filename>BBPATH</filename> defined, run
|
Now that you have <filename>BBPATH</filename> defined, run
|
||||||
the <filename>bitbake</filename> command again:
|
the <filename>bitbake</filename> command again:
|
||||||
<literallayout class='monospaced'>
|
<literallayout class='monospaced'>
|
||||||
@@ -313,7 +313,7 @@
|
|||||||
example, click on the links to take you to the definitions in
|
example, click on the links to take you to the definitions in
|
||||||
the glossary.
|
the glossary.
|
||||||
</para></listitem>
|
</para></listitem>
|
||||||
<listitem><para><emphasis>Run Bitbake:</emphasis>
|
<listitem><para><emphasis>Run BitBake:</emphasis>
|
||||||
After making sure that the <filename>conf/bitbake.conf</filename>
|
After making sure that the <filename>conf/bitbake.conf</filename>
|
||||||
file exists, you can run the <filename>bitbake</filename>
|
file exists, you can run the <filename>bitbake</filename>
|
||||||
command again:
|
command again:
|
||||||
@@ -364,7 +364,7 @@
|
|||||||
more depending on which build environments BitBake is
|
more depending on which build environments BitBake is
|
||||||
supporting.
|
supporting.
|
||||||
</para></listitem>
|
</para></listitem>
|
||||||
<listitem><para><emphasis>Run Bitbake:</emphasis>
|
<listitem><para><emphasis>Run BitBake:</emphasis>
|
||||||
After making sure that the <filename>classes/base.bbclass</filename>
|
After making sure that the <filename>classes/base.bbclass</filename>
|
||||||
file exists, you can run the <filename>bitbake</filename>
|
file exists, you can run the <filename>bitbake</filename>
|
||||||
command again:
|
command again:
|
||||||
@@ -434,7 +434,7 @@
|
|||||||
For more information on these variables, follow the links
|
For more information on these variables, follow the links
|
||||||
to the glossary.
|
to the glossary.
|
||||||
</para></listitem>
|
</para></listitem>
|
||||||
<listitem><para><emphasis>Run Bitbake With a Target:</emphasis>
|
<listitem><para><emphasis>Run BitBake With a Target:</emphasis>
|
||||||
Now that a BitBake target exists, run the command and provide
|
Now that a BitBake target exists, run the command and provide
|
||||||
that target:
|
that target:
|
||||||
<literallayout class='monospaced'>
|
<literallayout class='monospaced'>
|
||||||
@@ -468,7 +468,7 @@
|
|||||||
You need to provide your own information for
|
You need to provide your own information for
|
||||||
<filename>you</filename> in the file.
|
<filename>you</filename> in the file.
|
||||||
</para></listitem>
|
</para></listitem>
|
||||||
<listitem><para><emphasis>Run Bitbake With a Target:</emphasis>
|
<listitem><para><emphasis>Run BitBake With a Target:</emphasis>
|
||||||
Now that you have supplied the <filename>bblayers.conf</filename>
|
Now that you have supplied the <filename>bblayers.conf</filename>
|
||||||
file, run the <filename>bitbake</filename> command and provide
|
file, run the <filename>bitbake</filename> command and provide
|
||||||
the target:
|
the target:
|
||||||
|
|||||||
@@ -448,7 +448,7 @@
|
|||||||
<listitem><para><emphasis>Using the BitBake that Comes With Your
|
<listitem><para><emphasis>Using the BitBake that Comes With Your
|
||||||
Build Checkout:</emphasis>
|
Build Checkout:</emphasis>
|
||||||
A final possibility for getting a copy of BitBake is that it
|
A final possibility for getting a copy of BitBake is that it
|
||||||
already comes with your checkout of a larger Bitbake-based build
|
already comes with your checkout of a larger BitBake-based build
|
||||||
system, such as Poky.
|
system, such as Poky.
|
||||||
Rather than manually checking out individual layers and
|
Rather than manually checking out individual layers and
|
||||||
gluing them together yourself, you can check
|
gluing them together yourself, you can check
|
||||||
|
|||||||
@@ -5,7 +5,7 @@
|
|||||||
<title>Syntax and Operators</title>
|
<title>Syntax and Operators</title>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Bitbake files have their own syntax.
|
BitBake files have their own syntax.
|
||||||
The syntax has similarities to several
|
The syntax has similarities to several
|
||||||
other languages but also has some unique features.
|
other languages but also has some unique features.
|
||||||
This section describes the available syntax and operators
|
This section describes the available syntax and operators
|
||||||
@@ -1414,7 +1414,7 @@
|
|||||||
</section>
|
</section>
|
||||||
|
|
||||||
<section id='bitbake-style-python-functions-versus-python-functions'>
|
<section id='bitbake-style-python-functions-versus-python-functions'>
|
||||||
<title>Bitbake-Style Python Functions Versus Python Functions</title>
|
<title>BitBake-Style Python Functions Versus Python Functions</title>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Following are some important differences between
|
Following are some important differences between
|
||||||
@@ -1895,7 +1895,7 @@
|
|||||||
<para>
|
<para>
|
||||||
Sometimes, it is useful to be able to obtain information
|
Sometimes, it is useful to be able to obtain information
|
||||||
from the original execution environment.
|
from the original execution environment.
|
||||||
Bitbake saves a copy of the original environment into
|
BitBake saves a copy of the original environment into
|
||||||
a special variable named
|
a special variable named
|
||||||
<link linkend='var-bb-BB_ORIGENV'><filename>BB_ORIGENV</filename></link>.
|
<link linkend='var-bb-BB_ORIGENV'><filename>BB_ORIGENV</filename></link>.
|
||||||
</para>
|
</para>
|
||||||
@@ -2616,7 +2616,7 @@
|
|||||||
<para>
|
<para>
|
||||||
It is often necessary to access variables in the
|
It is often necessary to access variables in the
|
||||||
BitBake datastore using Python functions.
|
BitBake datastore using Python functions.
|
||||||
The Bitbake datastore has an API that allows you this
|
The BitBake datastore has an API that allows you this
|
||||||
access.
|
access.
|
||||||
Here is a list of available operations:
|
Here is a list of available operations:
|
||||||
</para>
|
</para>
|
||||||
|
|||||||
@@ -1780,7 +1780,7 @@
|
|||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Bitbake normally issues a warning when building two
|
BitBake normally issues a warning when building two
|
||||||
different recipes where each provides the same output.
|
different recipes where each provides the same output.
|
||||||
This scenario is usually something the user does not
|
This scenario is usually something the user does not
|
||||||
want.
|
want.
|
||||||
|
|||||||
Reference in New Issue
Block a user