Restructured the guide to follow a basic three step process: Set up, develop, build. All information that is independent of the OS selection was taken out of of the OS related documents and placed in the general set up sections. A new section, Developing Zephyr Applications, was added with links to all the development relevant section of the documentation. The content in local_development.rst was split between the setting_up.rst, installation_linux.rst and installation_mac.rst files as appropriate. This new structure provides a much better flow for developers beginning their Zephyr develpment. Applied all of Inaky's suggestions in the refactored content. Minor markup fixes and language edits were also perfomed during the refactoring. Fixed a cross-reference that was broken during the refactor. Applied all the feedback from the first trial run. Applied the feedback provided by David Kinder from TCS. Change-Id: I3368a3a41ec9ad02cc4e7b37fe71c65abd8a7df9 Signed-off-by: Rodrigo Caballero <rodrigo.caballero.abraham@intel.com>
27 lines
1.0 KiB
ReStructuredText
27 lines
1.0 KiB
ReStructuredText
.. _developing:
|
|
|
|
Developing Zephyr Applications
|
|
##############################
|
|
|
|
After setting up you development environment you are now ready to begin
|
|
developing your own Zephyr applications. To help you on this task, we provide
|
|
you with multiple resources:
|
|
|
|
The :ref:`application` section collects all the information you need to
|
|
develop, run and build your Zephyr applications.
|
|
|
|
The :ref:`contributing_code` section collects all the project's guidelines
|
|
regarding code collaboration, code style and Gerrit use. Be sure to test your
|
|
development before submitting it to Gerrit.
|
|
|
|
The :ref:`zephyr_primer` section contains detailed information regarding
|
|
micro- and nanokernel services and their functionality.
|
|
|
|
The :ref:`api` section contains the detailed information of all the available
|
|
APIs.
|
|
|
|
The :ref:`communication` section provides all the information regarding the
|
|
project's mailing list and bug tracking system.
|
|
|
|
The :ref:`documentation` section collects the project's documentation style
|
|
guides for in-code documentation and stand alone documentation. |