poky/documentation
Scott Rifenbark bd456271e4 documentation/adt-manual/adt-prepare.xml: Edits affecting rename and clarity
I made a pass through this chapter and focused on better descriptions for
getting the system ready for application development.  I made adjustments
to better represent what is really being done.  It is not all ADT here
as was being described before.  Miscellaneous edits and improvements
throughout.

(From yocto-docs rev: 3544beda4794005fe139d7620fd13618fab05534)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2012-07-18 12:43:51 +01:00
..
adt-manual documentation/adt-manual/adt-prepare.xml: Edits affecting rename and clarity 2012-07-18 12:43:51 +01:00
bsp-guide documentation/bsp-guide/bsp.xml: Updates to Kernel configuration section 2012-07-17 17:55:59 +01:00
dev-manual documentation/dev-manual/dev-manual-common-tasks.xml: Fixed reference 2012-07-17 10:54:12 +01:00
kernel-manual documentation/kernel-manual: Scrubbed the Yocto Project term 2012-07-03 14:55:02 +01:00
poky-ref-manual documentation: Changed link anchor for 'resourses' in QS 2012-07-17 17:55:59 +01:00
template documentation/pokt-ref-manual: Update with Yocto branding 2010-10-27 07:50:33 +01:00
tools documentation/tools: Add comments to script 2010-10-15 15:07:05 +01:00
yocto-project-qs documentation: Changed link anchor for 'resourses' in QS 2012-07-17 17:55:59 +01:00
Makefile documentation/Makefile: Fixed figures publishing bug 2012-05-01 20:50:56 +01:00
poky.ent documentation: Fixed the links to the BitBake Documentation page. 2012-07-17 10:54:10 +01:00
README documentation/README: Updates to explain development 2012-03-23 14:24:48 +00:00

documentation

This is the directory that contains the Yocto Project documentation. The Yocto Project source repositories at http://git.yoctoproject.org/cgit.cgi have two instances of the "documentation" directory. You should understand each of these instances.

poky/documentation - The directory within the poky Git repository containing the set of Yocto Project manuals. When you clone the poky Git repository, the documentation directory contains the manuals. The state of the manuals in this directory is guaranteed to reflect the latest Yocto Project release. The manuals at the tip of this directory will also likely contain most manual development changes.

yocto-docs/documentation - The Git repository for the Yocto Project manuals.
This repository is where manual development occurs. If you plan on contributing back to the Yocto Project documentation, you should set up a local Git repository based on this upstream repository as follows:

                           git clone git://git.yoctoproject.org/yocto-docs

                         Changes and patches are first pushed to the 
                         yocto-docs Git repository.  Later, they make it 
                         into the poky Git repository found at 
                         git://git.yoctoproject.org/poky.  

Manual Organization

Folders exist for individual manuals as follows:

  • adt-manual - The Yocto Project Application Development Toolkit (ADT) User's Guide.
  • bsp-guide - The Yocto Project Board Support (BSP) Developer's Guide
  • dev-manual - The Yocto Project Development Manual
  • kernel-manual - The Yocto Project Kernel Architecture and Use Manual
  • poky-ref-manual - The Yocto Project Reference Manual
  • yocto-project-qs - The Yocto Project Quick Start

Each folder is self-contained regarding content and figures.

Makefile

The Makefile processes manual directories to create HTML, PDF, tarballs, etc. Details on how the Makefile work are documented inside the Makefile. See that file for more information.

To build a manual, you run the make command and pass it the name of the folder containing the manual's contents. For example, the following command run from the documentation directory creates an HTML and a PDF version of the ADT manual. The DOC variable specifies the manual you are making:

 $ make DOC=adt-manual

poky.ent

This file defines variables used for documentation production. The variables are used to define release pathnames, URLs for the published manuals, etc.

template

Contains various templates, fonts, and some old PNG files.

tools

Contains a tool to convert the DocBook files to PDF format.