From eae7c2a0c277c764a72073cdce1cdb2eb1fd1b9a Mon Sep 17 00:00:00 2001 From: Michael Opdenacker Date: Wed, 4 May 2022 14:57:51 +0200 Subject: manuals: fix name capitalization issues - Using "BitBake" instead of "Bitbake" or "bitbake", aligning with the title of the "BitBake User Manual". - Using "OpenEmbedded" instead of "Openembedded" - Using "Python" instead of "python" (From yocto-docs rev: 0b893e2a15aefedd7100445fc9d7eeed07b6afc6) Signed-off-by: Michael Opdenacker Signed-off-by: Richard Purdie --- documentation/dev-manual/common-tasks.rst | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'documentation/dev-manual/common-tasks.rst') diff --git a/documentation/dev-manual/common-tasks.rst b/documentation/dev-manual/common-tasks.rst index 1da19b8d65..9b5a7536c1 100644 --- a/documentation/dev-manual/common-tasks.rst +++ b/documentation/dev-manual/common-tasks.rst @@ -5392,7 +5392,7 @@ create the properly partitioned image. The ``wic`` command generates partitioned images from existing OpenEmbedded build artifacts. Image generation is driven by partitioning -commands contained in an Openembedded kickstart file (``.wks``) +commands contained in an OpenEmbedded kickstart file (``.wks``) specified either directly on the command line or as one of a selection of canned kickstart files as shown with the ``wic list images`` command in the @@ -5464,7 +5464,7 @@ system needs to meet the following requirements: - You need to have the build artifacts already available, which typically means that you must have already created an image using the - Openembedded build system (e.g. ``core-image-minimal``). While it + OpenEmbedded build system (e.g. ``core-image-minimal``). While it might seem redundant to generate an image in order to create an image using Wic, the current version of Wic requires the artifacts in the form generated by the OpenEmbedded build system. @@ -5546,7 +5546,7 @@ Operational Modes ----------------- You can use Wic in two different modes, depending on how much control -you need for specifying the Openembedded build artifacts that are used +you need for specifying the OpenEmbedded build artifacts that are used for creating the image: Raw and Cooked: - *Raw Mode:* You explicitly specify build artifacts through Wic @@ -9214,7 +9214,7 @@ section: to run specific tasks in the build chain. It can be useful to run tasks "out-of-order" when trying isolate build issues. -- ":ref:`dev-manual/common-tasks:general bitbake problems`" describes how +- ":ref:`dev-manual/common-tasks:general BitBake problems`" describes how to use BitBake's ``-D`` debug output option to reveal more about what BitBake is doing during the build. @@ -9409,7 +9409,7 @@ format and can be converted to images (e.g. using the ``dot`` tool from - DOT files use a plain text format. The graphs generated using the ``bitbake -g`` command are often so large as to be difficult to - read without special pruning (e.g. with Bitbake's ``-I`` option) + read without special pruning (e.g. with BitBake's ``-I`` option) and processing. Despite the form and size of the graphs, the corresponding ``.dot`` files can still be possible to read and provide useful information. @@ -10560,7 +10560,7 @@ used testing branches for OpenEmbedded-Core are as follows: - *poky "master-next" branch:* This branch is part of the :yocto_git:`poky ` repository and combines proposed - changes to bitbake, the core metadata and the poky distro. + changes to BitBake, the core metadata and the poky distro. Similarly, stable branches maintained by the project may have corresponding ``-next`` branches which collect proposed changes. For example, @@ -11437,7 +11437,7 @@ this function, you have to follow the following steps: Please choose one that you want to use and enable the spdx task. You have to add some config options in ``local.conf`` file in your :term:`Build Directory`. Here is an example showing how to generate spdx files - during bitbake using the fossology-python.bbclass:: + during BitBake using the fossology-python.bbclass:: # Select fossology-python.bbclass. INHERIT += "fossology-python" -- cgit v1.2.3-54-g00ecf