zephyr/doc
Anas Nashif 2bc9d69981 build: abstract emulation and replace qemu goal with run
This will replace the current goal of 'make qemu' with 'make run' and
moves Qemu handling into its own file and into the boards instead of
being architecture specific.

We should be able to add new boards that support some other type of
emulation (by adding scripts/Makefile.<emu type>) and allow the board to
define their own options for the use type of emulation.

'make qemu' will still work, however it will be deprecated, starting
with this commit it is recommended to use 'make run'.

Jira: ZEP-359
Change-Id: I1cacd56b4ec09421a58cf5d010e22e9035214df6
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2017-01-10 20:20:47 +00:00
..
api
application build: abstract emulation and replace qemu goal with run 2017-01-10 20:20:47 +00:00
contribute
crypto
drivers
getting_started build: abstract emulation and replace qemu goal with run 2017-01-10 20:20:47 +00:00
introduction boards: prepare for integration of board documentation 2017-01-10 02:45:54 +00:00
kernel
porting
reference/kconfig
scripts/genrest
subsystems build: abstract emulation and replace qemu goal with run 2017-01-10 20:20:47 +00:00
templates boards: prepare for integration of board documentation 2017-01-10 02:45:54 +00:00
themes/zephyr
conf.py
doxygen.config
LICENSING.rst doc: move documetnation context to root directory 2017-01-06 22:51:31 +00:00
Makefile doc: move documetnation context to root directory 2017-01-06 22:51:31 +00:00
README.rst doc: fix documentation target and instructions 2017-01-09 16:20:21 +00:00
release-notes.rst doc: move documetnation context to root directory 2017-01-06 22:51:31 +00:00

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

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

To install ReadTheDocs.org theme, use pip to install the python package:

.. code-block:: bash

   $ pip install sphinx_rtd_theme

If the above theme is installed, it will be used instead of the default theme.

.. 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
``<ZEPHYR_BASE>``, type:

.. code-block:: bash

   $ cd <ZEPHYR_BASE>
   $ make htmldocs

Find the output in ``<ZEPHYR_BASE>/doc/_build/html/index.html``

Review the available formats with:

.. code-block:: bash

   $ make -C <ZEPHYR_BASE>/doc help

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