From: Ilya Maximets
Current documentation uses syntax highlighting in 'sphinx'
via 'pygments' library. This leads to build failures on the
systems with old version of this library.
In fact that only 'windows.rst' uses highlighting it's a
very simple change. This helps us to avoid build issues
on different systems and allows to remove painful external
dependency.
Signed-off-by: Ilya Maximets
Signed-off-by: Ben Pfaff
(cherry picked from commit 23cb93ff917e2addfed497730a8e72f261e677ce)
---
Documentation/conf.py | 3 -
.../internals/contributing/documentation-style.rst | 10 ++-
Documentation/intro/install/windows.rst| 88 +++---
Documentation/topics/language-bindings.rst | 2 +-
4 files changed, 51 insertions(+), 52 deletions(-)
diff --git a/Documentation/conf.py b/Documentation/conf.py
index 389ef70..ab439cf 100644
--- a/Documentation/conf.py
+++ b/Documentation/conf.py
@@ -107,9 +107,6 @@ exclude_patterns = ['_build', 'Thumbs.db', '.DS_Store']
#
# show_authors = False
-# The name of the Pygments (syntax highlighting) style to use.
-# pygments_style = 'friendly'
-
# A list of ignored prefixes for module index sorting.
# modindex_common_prefix = []
diff --git a/Documentation/internals/contributing/documentation-style.rst
b/Documentation/internals/contributing/documentation-style.rst
index ea41a07..99eec69 100644
--- a/Documentation/internals/contributing/documentation-style.rst
+++ b/Documentation/internals/contributing/documentation-style.rst
@@ -115,9 +115,11 @@ Titles
Code
-- Use ``::``, the ``code`` role or the ``code-block:: `` role to prefix
- code. The ``code-block:: `` format is preferred as this provides
- syntax highlighting for non-Python languages, such as Bash or PowerShell.
+- Use ``::`` to prefix code.
+
+- Don't use syntax highlighting such as ``.. highlight:: `` or
+ ``code-block:: `` because it depends on external ``pygments``
+ library.
- Prefix commands with ``$``.
@@ -259,7 +261,7 @@ Figures and Other Media
- All images should be in PNG format and compressed where possible. For PNG
files, use OptiPNG and AdvanceCOMP's ``advpng``:
- .. code-block:: shell
+ ::
$ optipng -o7 -zm1-9 -i0 -strip all
$ advpng -z4
diff --git a/Documentation/intro/install/windows.rst
b/Documentation/intro/install/windows.rst
index caa9f40..2be4eb5 100644
--- a/Documentation/intro/install/windows.rst
+++ b/Documentation/intro/install/windows.rst
@@ -63,7 +63,7 @@ The following explains the steps in some detail.
We require that you have Python six and pypiwin32 libraries installed.
The libraries can be installed via pip command:
- .. code-block:: console
+ ::
$ pip install six
$ pip install pypiwin32
@@ -140,7 +140,7 @@ you pulled the sources directly from an Open vSwitch Git
tree or got a
Git tree snapshot, then run boot.sh in the top source directory to build
the "configure" script:
-.. code-block:: console
+::
$ ./boot.sh
@@ -153,7 +153,7 @@ Configure the package by running the configure script. You
should provide some
configure options to choose the right compiler, linker, libraries, Open vSwitch
component installation directories, etc. For example:
-.. code-block:: console
+::
$ ./configure CC=./build-aux/cccl LD="$(which link)" \
LIBS="-lws2_32 -liphlpapi -lwbemuuid -lole32 -loleaut32" \
@@ -169,7 +169,7 @@ component installation directories, etc. For example:
To configure with SSL support, add the requisite additional options:
-.. code-block:: console
+::
$ ./configure CC=./build-aux/cccl LD="`which link`" \
LIBS="-lws2_32 -liphlpapi -lwbemuuid -lole32 -loleaut32" \
@@ -181,7 +181,7 @@ To configure with SSL support, add the requisite additional
options:
Finally, to the kernel module also:
-.. code-block:: console
+::
$ ./configure CC=./build-aux/cccl LD="`which link`" \
LIBS="-lws2_32 -liphlpapi -lwbemuuid -lole32 -loleaut32" \
@@ -211,7 +211,7 @@ building on Linux, FreeBSD, or NetBSD.
#. Run make for the ported executables in the top source directory, e.g.:
- .. code-block:: console
+ ::
$ make
@@ -225,25 +225,25 @@ building on Linux, FreeBSD, or NetBSD.
all MinGW sessions and then run the below command from MSVC developers
command prompt.:
- .. code-block:: doscon
+ ::
> mingw-get upgrade msys-core-bin=1.0.17-1
#. To run all the unit tests in Open vSwitch, one at a time:
- .. code-block:: console
+ ::
$ make check
To run all the unit tests in Open vSwitch, up to 8 in parallel:
- .. code-block:: console
+ ::
$ make check TESTSUITEFLAGS="-j8"
#. To install all the compiled executables on the local machine, run:
- .. code-block:: console
+ ::
$ make install
@@ -276,7 +276,7 @@ Now run ``./uninstall.cmd`` to