mirror of
https://git.yoctoproject.org/poky
synced 2026-06-01 13:09:50 +00:00
manuals: code insertion simplification over two lines
This simplifies paragraphs ending with a colon and followed by code insertion. Automatically substituted through the command: sed -i -z "s/:\n\s*::/::/g" file.rst This generates identical HTML output. (From yocto-docs rev: 28e2192a7c12d64b68061138a9f6c796453eebb1) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
committed by
Richard Purdie
parent
773536c333
commit
c3c6de2187
@@ -120,8 +120,7 @@ supported Ubuntu or Debian Linux distribution:
|
||||
might experience QEMU build failures due to the package installing
|
||||
its own custom ``/usr/include/linux/soundcard.h`` on the Debian
|
||||
system. If you run into this situation, either of the following
|
||||
solutions exist:
|
||||
::
|
||||
solutions exist::
|
||||
|
||||
$ sudo apt-get build-dep qemu
|
||||
$ sudo apt-get remove oss4-dev
|
||||
@@ -132,14 +131,12 @@ supported Ubuntu or Debian Linux distribution:
|
||||
|
||||
$ sudo pip3 install GitPython pylint==1.9.5
|
||||
|
||||
- *Essentials:* Packages needed to build an image on a headless system:
|
||||
::
|
||||
- *Essentials:* Packages needed to build an image on a headless system::
|
||||
|
||||
$ sudo apt-get install &UBUNTU_HOST_PACKAGES_ESSENTIAL;
|
||||
|
||||
- *Documentation:* Packages needed if you are going to build out the
|
||||
Yocto Project documentation manuals:
|
||||
::
|
||||
Yocto Project documentation manuals::
|
||||
|
||||
$ sudo apt-get install make python3-pip
|
||||
&PIP3_HOST_PACKAGES_DOC;
|
||||
@@ -157,14 +154,12 @@ The following list shows the required packages by function given a
|
||||
supported Fedora Linux distribution:
|
||||
|
||||
- *Essentials:* Packages needed to build an image for a headless
|
||||
system:
|
||||
::
|
||||
system::
|
||||
|
||||
$ sudo dnf install &FEDORA_HOST_PACKAGES_ESSENTIAL;
|
||||
|
||||
- *Documentation:* Packages needed if you are going to build out the
|
||||
Yocto Project documentation manuals:
|
||||
::
|
||||
Yocto Project documentation manuals::
|
||||
|
||||
$ sudo dnf install make python3-pip which
|
||||
&PIP3_HOST_PACKAGES_DOC;
|
||||
@@ -176,14 +171,12 @@ The following list shows the required packages by function given a
|
||||
supported openSUSE Linux distribution:
|
||||
|
||||
- *Essentials:* Packages needed to build an image for a headless
|
||||
system:
|
||||
::
|
||||
system::
|
||||
|
||||
$ sudo zypper install &OPENSUSE_HOST_PACKAGES_ESSENTIAL;
|
||||
|
||||
- *Documentation:* Packages needed if you are going to build out the
|
||||
Yocto Project documentation manuals:
|
||||
::
|
||||
Yocto Project documentation manuals::
|
||||
|
||||
$ sudo zypper install make python3-pip which
|
||||
&PIP3_HOST_PACKAGES_DOC;
|
||||
@@ -196,8 +189,7 @@ The following list shows the required packages by function given a
|
||||
supported CentOS-7 Linux distribution:
|
||||
|
||||
- *Essentials:* Packages needed to build an image for a headless
|
||||
system:
|
||||
::
|
||||
system::
|
||||
|
||||
$ sudo yum install &CENTOS7_HOST_PACKAGES_ESSENTIAL;
|
||||
|
||||
@@ -212,8 +204,7 @@ supported CentOS-7 Linux distribution:
|
||||
``epel-release``.
|
||||
|
||||
- *Documentation:* Packages needed if you are going to build out the
|
||||
Yocto Project documentation manuals:
|
||||
::
|
||||
Yocto Project documentation manuals::
|
||||
|
||||
$ sudo yum install make python3-pip which
|
||||
&PIP3_HOST_PACKAGES_DOC;
|
||||
@@ -225,8 +216,7 @@ The following list shows the required packages by function given a
|
||||
supported CentOS-8 Linux distribution:
|
||||
|
||||
- *Essentials:* Packages needed to build an image for a headless
|
||||
system:
|
||||
::
|
||||
system::
|
||||
|
||||
$ sudo dnf install &CENTOS8_HOST_PACKAGES_ESSENTIAL;
|
||||
|
||||
@@ -244,8 +234,7 @@ supported CentOS-8 Linux distribution:
|
||||
``epel-release``.
|
||||
|
||||
- *Documentation:* Packages needed if you are going to build out the
|
||||
Yocto Project documentation manuals:
|
||||
::
|
||||
Yocto Project documentation manuals::
|
||||
|
||||
$ sudo dnf install make python3-pip which
|
||||
&PIP3_HOST_PACKAGES_DOC;
|
||||
@@ -287,8 +276,7 @@ The ``install-buildtools`` script is the easiest of the three methods by
|
||||
which you can get these tools. It downloads a pre-built buildtools
|
||||
installer and automatically installs the tools for you:
|
||||
|
||||
1. Execute the ``install-buildtools`` script. Here is an example:
|
||||
::
|
||||
1. Execute the ``install-buildtools`` script. Here is an example::
|
||||
|
||||
$ cd poky
|
||||
$ scripts/install-buildtools --without-extended-buildtools \
|
||||
@@ -302,22 +290,19 @@ installer and automatically installs the tools for you:
|
||||
installation is functional.
|
||||
|
||||
To avoid the need of ``sudo`` privileges, the ``install-buildtools``
|
||||
script will by default tell the installer to install in:
|
||||
::
|
||||
script will by default tell the installer to install in::
|
||||
|
||||
/path/to/poky/buildtools
|
||||
|
||||
If your host development system needs the additional tools provided
|
||||
in the ``buildtools-extended`` tarball, you can instead execute the
|
||||
``install-buildtools`` script with the default parameters:
|
||||
::
|
||||
``install-buildtools`` script with the default parameters::
|
||||
|
||||
$ cd poky
|
||||
$ scripts/install-buildtools
|
||||
|
||||
2. Source the tools environment setup script by using a command like the
|
||||
following:
|
||||
::
|
||||
following::
|
||||
|
||||
$ source /path/to/poky/buildtools/environment-setup-x86_64-pokysdk-linux
|
||||
|
||||
@@ -342,13 +327,11 @@ steps:
|
||||
1. Locate and download the ``*.sh`` at &YOCTO_RELEASE_DL_URL;/buildtools/
|
||||
|
||||
2. Execute the installation script. Here is an example for the
|
||||
traditional installer:
|
||||
::
|
||||
traditional installer::
|
||||
|
||||
$ sh ~/Downloads/x86_64-buildtools-nativesdk-standalone-&DISTRO;.sh
|
||||
|
||||
Here is an example for the extended installer:
|
||||
::
|
||||
Here is an example for the extended installer::
|
||||
|
||||
$ sh ~/Downloads/x86_64-buildtools-extended-nativesdk-standalone-&DISTRO;.sh
|
||||
|
||||
@@ -357,8 +340,7 @@ steps:
|
||||
``/home/your-username/buildtools``
|
||||
|
||||
3. Source the tools environment setup script by using a command like the
|
||||
following:
|
||||
::
|
||||
following::
|
||||
|
||||
$ source /home/your_username/buildtools/environment-setup-i586-poky-linux
|
||||
|
||||
@@ -390,13 +372,11 @@ installer:
|
||||
your build environment with the setup script
|
||||
(:ref:`structure-core-script`).
|
||||
|
||||
2. Run the BitBake command to build the tarball:
|
||||
::
|
||||
2. Run the BitBake command to build the tarball::
|
||||
|
||||
$ bitbake buildtools-tarball
|
||||
|
||||
or run the BitBake command to build the extended tarball:
|
||||
::
|
||||
or run the BitBake command to build the extended tarball::
|
||||
|
||||
$ bitbake buildtools-extended-tarball
|
||||
|
||||
@@ -415,13 +395,11 @@ installer:
|
||||
|
||||
4. On the machine that does not meet the requirements, run the ``.sh``
|
||||
file to install the tools. Here is an example for the traditional
|
||||
installer:
|
||||
::
|
||||
installer::
|
||||
|
||||
$ sh ~/Downloads/x86_64-buildtools-nativesdk-standalone-&DISTRO;.sh
|
||||
|
||||
Here is an example for the extended installer:
|
||||
::
|
||||
Here is an example for the extended installer::
|
||||
|
||||
$ sh ~/Downloads/x86_64-buildtools-extended-nativesdk-standalone-&DISTRO;.sh
|
||||
|
||||
@@ -430,8 +408,7 @@ installer:
|
||||
``/home/your_username/buildtools``
|
||||
|
||||
5. Source the tools environment setup script by using a command like the
|
||||
following:
|
||||
::
|
||||
following::
|
||||
|
||||
$ source /home/your_username/buildtools/environment-setup-x86_64-poky-linux
|
||||
|
||||
|
||||
Reference in New Issue
Block a user