diff options
| -rw-r--r-- | bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml | 2 | ||||
| -rw-r--r-- | bitbake/doc/bitbake-user-manual/bitbake-user-manual-ref-variables.xml | 6 |
2 files changed, 4 insertions, 4 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 e4cc422ea4..f1caaecd2d 100644 --- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml +++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-execution.xml @@ -781,7 +781,7 @@ 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 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". By default, there is a dummy "noop" signature handler enabled in BitBake. This means that behavior is unchanged from previous versions. 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 cee6c94753..0313359d98 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 @@ -78,7 +78,7 @@ </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. An example is <filename>git-native</filename>, which 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 of the software. 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 Quilt built to run on the build system; "crosses" such as <filename>gcc-cross</filename>, which is a compiler @@ -980,7 +980,7 @@ amount of code, it usually is as simple as adding the variable to your recipe. Here are two examples. - The "native" variants are from the OpenEmbedded Core + The "native" variants are from the OpenEmbedded-Core metadata: <literallayout class='monospaced'> BBCLASSEXTEND =+ "native nativesdk" |