mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-05-31 12:49:46 +00:00
Code Issues Projects Releases Wiki Activity

bitbake: bitbake-user-manual: Updated "OpenEmbedded-Core" term.

Browse Source 
Made sure that the terms "OpenEmbedded-Core" and "OE-Core"
are used as such throughout the manual.

(Bitbake rev: 677e58f8616a4bf58772e54d2313af3885a3b110)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2018-04-07 14:38:42 -07:00
committed by Richard Purdie
parent 0a0d01addd
commit adde339596
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml
+1 -1
View File
@@ -781,7 +781,7 @@
The code in <filename>meta/lib/oe/sstatesig.py</filename> shows two examples The code in <filename>meta/lib/oe/sstatesig.py</filename> shows two examples
of this and also illustrates how you can insert your own policy into the system of this and also illustrates how you can insert your own policy into the system
if so desired. if so desired.
This file defines the two basic signature generators OpenEmbedded Core This file defines the two basic signature generators OpenEmbedded-Core
uses: "OEBasic" and "OEBasicHash". uses: "OEBasic" and "OEBasicHash".
By default, there is a dummy "noop" signature handler enabled in BitBake. By default, there is a dummy "noop" signature handler enabled in BitBake.
This means that behavior is unchanged from previous versions. This means that behavior is unchanged from previous versions.
bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml
+3 -3
View File
@@ -78,7 +78,7 @@
</para> </para>
<para> <para>
In OpenEmbedded Core, <filename>ASSUME_PROVIDED</filename> In OpenEmbedded-Core, <filename>ASSUME_PROVIDED</filename>
mostly specifies native tools that should not be built. mostly specifies native tools that should not be built.
An example is <filename>git-native</filename>, which An example is <filename>git-native</filename>, which
when specified allows for the Git binary from the host to when specified allows for the Git binary from the host to
@@ -964,7 +964,7 @@
Allows you to extend a recipe so that it builds variants Allows you to extend a recipe so that it builds variants
of the software. of the software.
Some examples of these variants for recipes from the Some examples of these variants for recipes from the
OpenEmbedded Core metadata are "natives" such as OpenEmbedded-Core metadata are "natives" such as
<filename>quilt-native</filename>, which is a copy of <filename>quilt-native</filename>, which is a copy of
Quilt built to run on the build system; "crosses" such Quilt built to run on the build system; "crosses" such
as <filename>gcc-cross</filename>, which is a compiler as <filename>gcc-cross</filename>, which is a compiler
@@ -980,7 +980,7 @@
amount of code, it usually is as simple as adding the amount of code, it usually is as simple as adding the
variable to your recipe. variable to your recipe.
Here are two examples. Here are two examples.
The "native" variants are from the OpenEmbedded Core The "native" variants are from the OpenEmbedded-Core
metadata: metadata:
<literallayout class='monospaced'> <literallayout class='monospaced'>
BBCLASSEXTEND =+ "native nativesdk" BBCLASSEXTEND =+ "native nativesdk"