zephyr/doc
Andre Guedes 3f9d4752c6 doc: Add returning code conventions
Zephyr now uses codes from errno.h as the standard returning code for
all APIs. Since some code usages can be confusing or ambiguous, this
patch documents the conventions we are using to keep the returning code
usage consistent.

The document is based on the current mapping we have in device.h.

Change-Id: Ie6f429602592be8572631e34ae65435530a05b9f
Signed-off-by: Andre Guedes <andre.guedes@intel.com>
2016-03-30 20:03:17 +00:00
..
api docs: fixed API linking 2016-02-16 06:16:48 +00:00
application doc: fix path to samples after restructering 2016-02-11 13:08:44 -05:00
bluetooth Bluetooth: doc: Add L2CAP PICS file 2016-02-16 13:50:00 +01:00
board doc: arduino_due: explain how to build the bossac tool ... 2016-03-08 00:41:32 +00:00
collaboration doc: Add returning code conventions 2016-03-30 20:03:17 +00:00
crypto docs: fixed crypto headline and bullet indentation 2016-02-25 21:28:58 +00:00
getting_started docs: clarify MINGW installation instructions 2016-03-29 11:06:52 +00:00
kernel kernel: Combine nano_timers and nano_timeouts 2016-03-26 09:20:10 +00:00
reference doc: Remove orphaned kbuild_toolchains.rst 2016-02-18 22:58:07 +00:00
scripts/genrest doc: Documentation generator failed for html format 2016-03-01 16:53:51 +00:00
themes/zephyr
Makefile docs: fixed errors when building docs 2016-02-25 21:28:58 +00:00
README.rst
about_zephyr.rst trivial: fixed typo: sempahores -> semaphores 2016-02-09 18:04:36 +00:00
conf.py doc: Fixed two warnings in html format documentation generation 2016-03-02 12:33:44 +00:00
doxygen.config doc: Edit the Event Logger APIs 2016-02-12 01:41:20 +00:00
index.rst doc: Fix headings in master index file. 2016-02-08 16:16:59 -05:00
substitutions.rst

README.rst

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
*******************

The project's documentation currently comprises the following items:

* An Installation Guide for Linux host systems

* A set of Collaboration Guidelines for the project.

* Doxygen output from the code base for all APIs.

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

Install the current version of ``Sphinx``, type:

.. code-block:: bash

   $ git clone https://github.com/sphinx-doc/sphinx.git sphinx

   $ cd sphinx

   $ sudo -E python setup.py install

   $ cd ..

   $ git clone https://github.com/michaeljones/breathe.git breathe

   $ cd breathe

   $ sudo -E python setup.py install

.. note::

   Make sure that ``Doxygen`` is installed in your system.
   The installation of Doxygen is beyond the scope of this document.

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

Assuming that the Zephyr Project tree with the doc directory is in
``DIRECTORY``, type:

.. code-block:: bash

   $ cd DIRECTORY/doc

   $ make doxy html

Find the output in ``DIRECTORY/doc/_build/html/index.html``

Review the available formats with:

.. code-block:: bash

   $ make -C DIRECTORY/doc doxy html

If you want the LaTeX PDF output, you need to install all the Latex
packages first. That installation is beyond the scope of this document.

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