Scott Rifenbark 2f25c9b56c yocto-project-qs: Added section for CROPS. 7 年之前
..
adt-manual ccc830df1d documentation: Prepare for 2.1 builds 9 年之前
bsp-guide 56b3c79a3e bsp-guide: Minor introduction rewrite and formatting BSP workflow. 8 年之前
dev-manual 6d7b42f650 dev-manual: Added Links for specific container use 7 年之前
kernel-dev 609f23d81b kernel-dev: Added the "writernotes" style. 8 年之前
mega-manual f4aa9783bd yocto-project-qs, ref-manual: Moved YP intro from QS to ref-manual 7 年之前
profile-manual 374f3d6be2 Documentation: Created YP 2.4 "latest" docs 8 年之前
ref-manual f4aa9783bd yocto-project-qs, ref-manual: Moved YP intro from QS to ref-manual 7 年之前
sdk-manual 33969a3c92 sdk-manual: Converted extracting root filesystem to procedure 7 年之前
template 85a0b9b941 toaster-manual: Draft of Manual. 10 年之前
toaster-manual 74bf586c94 documentation: Fixed links for "build-directory" term. 8 年之前
tools 374f3d6be2 Documentation: Created YP 2.4 "latest" docs 8 年之前
yocto-project-qs 2f25c9b56c yocto-project-qs: Added section for CROPS. 7 年之前
Makefile f4aa9783bd yocto-project-qs, ref-manual: Moved YP intro from QS to ref-manual 7 年之前
README d9b4c804be README: Updated to remove the ADT manual and add the SDK manual. 9 年之前
poky.ent 5a402f9d1b poky.ent: Updated CentOS required package 7 年之前

README

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:

* sdk-manual - The Yocto Project Software Development Kit (SDK) Developer's Guide.
* bsp-guide - The Yocto Project Board Support Package (BSP) Developer's Guide
* dev-manual - The Yocto Project Development Manual
* kernel-dev - The Yocto Project Linux Kernel Development Manual
* ref-manual - The Yocto Project Reference Manual
* yocto-project-qs - The Yocto Project Quick Start
* mega-manual - The Yocto Project Mega-Manual, which is an aggregated manual comprised
of all YP manuals and guides
* profile-manual - The Yocto Project Profile and Tracing Manual
* toaster-manual - The Toaster Manual

Each folder is self-contained regarding content and figures. Note that there
is a sed file needed to process the links of the mega-manual. The sed file
is located in the tools directory. Also note that the figures folder in the
mega-manual directory contains duplicates of all the figures in the YP folders
directories for all YP manuals and guides.

If you want to find HTML versions of the Yocto Project manuals on the web,
go to http://www.yoctoproject.org and click on the "Documentation" tab. From
there you have access to archived documentation from previous releases, current
documentation for the latest release, and "Docs in Progress" for the release
currently being developed.

In general, the Yocto Project site (http://www.yoctoproject.org) is a great
reference for both information and downloads.

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 version of the SDK manual.
The DOC variable specifies the manual you are making:

$ make DOC=sdk-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. This folder also
contains the mega-manual.sed file, which is used by Makefile to process
cross-references from within the manual that normally go to an external
manual.