zephyr/doc
Johan Hedberg 6714e88788 doc: arduino_101: Add link to BlueZ 5.40
Change-Id: I83e6a51e276cb68bbd02e6e184faf76b596f1449
Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-05-27 07:31:44 +00:00
..
api doc: Restructure top level sections. 2016-05-21 21:22:46 +00:00
application
bluetooth
board doc: arduino_101: Add link to BlueZ 5.40 2016-05-27 07:31:44 +00:00
contribute doc: collaboration: code: gerrit commit message JIRA key 2016-04-18 20:25:40 +00:00
crypto
drivers device: add macro to assign driver_api at compile time 2016-04-15 22:06:09 +00:00
getting_started doc: Restructure top level sections. 2016-05-21 21:22:46 +00:00
kernel doc : Corrections to memory_map doc page 2016-05-26 10:58:11 +00:00
porting doc: Edit arch.rst markup 2016-05-03 13:09:16 -05:00
reference doc: Restructure top level sections. 2016-05-21 21:22:46 +00:00
scripts/genrest doc: use table for Kconfig option reference 2016-05-11 15:15:44 +00:00
subsystems doc: fixed bullet list for bluetooth 2016-04-30 09:48:49 -04:00
themes/zephyr
about_zephyr.rst
conf.py doc: sphinx conf: use env var in sphinx doc version 2016-04-13 23:42:18 +00:00
doxygen.config kernel event logger: add possibility to use custom timestamp 2016-05-23 21:27:49 +00:00
index.rst doc: Restructure top level sections. 2016-05-21 21:22:46 +00:00
Makefile doc: show information about documentation current version 2016-04-22 10:54:38 +00:00
README.rst
substitutions.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