c6bb463995
The section describing how to set up meta-intel has been re-written to provide more information about this Git repository and why it is important. Also, added information explaining why user should use the same set up method (tarball or Git repo) as used to set up the YP files tree. Reported-by: Robert P. J. Day <rpjday@crashcourse.ca> (From yocto-docs rev: 53fbfc59f0183a6b8474ed643302faffef79356b) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
documentation
This is the location for the Yocto Project documentation. Documentation consists of six manuals (see below).
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.