zephyr/doc
David B. Kinder d3b0cd4827 doc: move docgen filter out of shippable script
Because of known issues with Sphinx/Breathe tools we're using to
generate doxygen-based comments for our API documentation, we're getting
a bevy of warning messages written out. As a workaround for our CI
system, we created a filter-known-issues.py script to remove "expected"
warnings from the output.

This patch moves calling that filter script into the doc generation
Makefile so folks making local builds of the docs won't be tripped up by
all the warning messages either.  Output of the "make htmldocs" command
is now filtered so only "unexpected" errors and warnings will be shown.

(See https://github.com/sphinx-doc/sphinx/issue/2682 and
sphinx-doc/sphinx#2683i for the Sphinx/Breathe issues.)

Fixes #1527

Signed-off-by: David B. Kinder <david.b.kinder@intel.com>
2017-09-22 08:07:30 -04:00
..
api doc: improve API docs with sections 2017-09-12 07:48:37 -04:00
application doc: fix misspellings and hyphen use 2017-09-20 15:33:43 -04:00
contribute doc: add project security docs 2017-08-17 23:20:40 -04:00
crypto doc: fix more spelling errors throughout docs 2017-02-28 13:22:13 +00:00
devices doc: move device drivers, model and tree in one section 2017-08-18 16:32:28 -04:00
getting_started doc: fix misspellings and hyphen use 2017-09-20 15:33:43 -04:00
introduction doc: fix misspellings and hyphen use 2017-09-20 15:33:43 -04:00
kernel doc: fix misspellings and hyphen use 2017-09-20 15:33:43 -04:00
porting doc: spelling fixes in docs 2017-08-02 15:14:13 -04:00
reference/kconfig
scripts doc: move docgen filter out of shippable script 2017-09-22 08:07:30 -04:00
security doc: fix misspellings and hyphen use 2017-09-20 15:33:43 -04:00
static doc: tweak API doc CSS for RTD theme 2017-09-13 09:14:21 -04:00
subsystems net: Improve documentation about accessing Internet from qemu. 2017-09-22 08:01:44 -04:00
templates doc: fix .rst files canonical heading order 2017-01-20 16:06:36 -08:00
themes/zephyr
tools kconfig: remove empty and unused kernel.config 2017-08-03 07:19:29 -05:00
404.rst doc: add custom 404 page 2017-08-18 21:41:45 -04:00
LICENSING.rst doc: remove use of :download: directive 2017-08-22 08:34:37 -04:00
Makefile doc: move docgen filter out of shippable script 2017-09-22 08:07:30 -04:00
README.rst doc: add python pip requirements.txt 2017-07-22 14:04:20 -04:00
Zephyr-Kite-in-tree.png doc: add custom 404 page 2017-08-18 21:41:45 -04:00
conf.py doc: fix sphinx 1.5 broken search box 2017-08-22 16:28:53 -04:00
copyright.rst doc: update copyright for documentation 2017-01-31 21:35:29 +00:00
glossary.rst doc: simplify top level TOC 2017-08-18 16:32:28 -04:00
index.rst doc: add 1.9.0 docs link to index page 2017-09-07 18:27:51 -05:00
release-notes-1.5.rst doc: update to use macOS throughout docs 2017-09-15 17:21:47 -04:00
release-notes-1.6.rst doc: spelling fixes in docs 2017-08-02 15:14:13 -04:00
release-notes-1.7.rst doc: spelling fixes in docs 2017-08-02 15:14:13 -04:00
release-notes-1.8.rst doc: spelling fixes in docs 2017-08-02 15:14:13 -04:00
release-notes-1.9.rst doc: fix misspellings and hyphen use 2017-09-20 15:33:43 -04:00
release-notes.rst doc: update release notes index with 1.9 2017-09-12 13:19:51 -04:00
zephyr.doxyfile doc: exclude spi_legacy.h from API docs 2017-09-10 09:18:01 -04:00

README.rst

:orphan:

Welcome to Zephyr Kernel
########################

.. This document is in Restructured Text Format.
   Find more information regarding the ReST markup in the
   `ReST documentation`_.
   This is a comment that won't show up in formatted output

Welcome to the Zephyr Project.

Thank you for your interest in the Zephyr Project. These instructions are
designed to walk you through generating the Zephyr Project's documentation.

Documentation Notes
*******************

Zephyr Project content is written using the reStructuredText markup language
(.rst file extension) with Sphinx extensions, and processed using sphinx to
create a formatted stand-alone website. Developers can view this content either
in its raw form as .rst markup files, or you can generate the HTML content and view it
with a web browser directly on your workstations drive. This same .rst
content is also fed into the Zephyr Project's public website documentation area
(with a different theme applied).

You can read details about reStructuredText and about Sphinx extensions from
their respective websites.

The project's documentation currently comprises the following items:

* ReStructuredText source files used to generate documentation found at
  https://zephyrproject.org/doc website. Most of the reStructuredText sources
  are found in the ``/doc`` directory, but there are others stored within the
  code source tree near their specific component (such as ``/samples`` and
  ``/boards``)

* Doxygen-generated material used to create all API-specific documents
  also found at https://zephyrproject.org/doc

* Script-generated material for kernel configuration options based on kconfig
  files found in the source code tree

The reStructuredText files are processed by the Sphinx documentation system,
and make use of the breathe extension for including the doxygen-generated API
material.  Additional tools are required to generate the
documentation locally, as described in the following sections.

Installing the documentation processors
***************************************

Our documentation processing has been tested to run with:

* Doxygen version 1.8.10 (and 1.8.11)
* Sphinx version 1.4.4 (but not with 1.5.1)
* Breathe version 4.4.0
* docutils version 0.12 (0.13 has issues with Sphinx 1.4.4)

Begin by cloning a copy of the git repository for the zephyr project and
setting up your development environment as described in :ref:`getting_started`
or specifically for Ubuntu in :ref:`installation_linux`.  (Be sure to
export the environment variables ``ZEPHYR_GCC_VARIANT`` and
``ZEPHYR_SDK_INSTALL_DIR`` as documented there.)

Here are a set of commands to install the documentation generations tools on
Ubuntu:

.. code-block:: bash

   $ sudo -E apt-get install doxygen
   $ curl -O 'https://bootstrap.pypa.io/get-pip.py'
   $ ./get-pip.py
   $ rm get-pip.py
   $ pip install -r scripts/requirements.txt


Running the Documentation Generators
************************************

The ``/doc`` directory in your cloned copy of zephyr project git repo has all the
.rst source files, extra tools, and Makefile for generating a local copy of
the Zephyr project's technical documentation.  Assuming the local Zephyr
project copy is ``~/zephyr``, here are the commands to generate the html
content locally:

.. code-block:: bash

   $ cd ~/zephyr
   $ source zephyr-env.sh
   $ make htmldocs

The html output will be in ``~/zephyr/doc/_build/html/index.html``


.. _ReST documentation: http://sphinx-doc.org/rest.html