Scott Rifenbark 444dc2e99b bitbake: bitbake-user-manual: Fixed porno hack for hello world example 7 lat temu
..
bitbake-user-manual 444dc2e99b bitbake: bitbake-user-manual: Fixed porno hack for hello world example 7 lat temu
template 49b416dde5 bitbake: templates: Added newline character to end of script. 11 lat temu
tools 034e49004f bitbake: user-manual: Import YP Docs templates for usermanual improvements 11 lat temu
COPYING.GPL f5665d5bfc bitbake: Sync with upstream. 18 lat temu
COPYING.MIT f54da734eb Initial population 20 lat temu
Makefile 961e692cf2 bitbake: Makefile: Updated the script to not create PDF version by default 10 lat temu
README 392de9d568 bitbake: doc: Rename user-manual -> bitbake-user-manual 11 lat temu
bitbake.1 653b557770 bitbake: "per-package" should say "per-recipe" 11 lat temu
poky.ent 034e49004f bitbake: user-manual: Import YP Docs templates for usermanual improvements 11 lat temu

README

Documentation
=============

This is the directory that contains the BitBake documentation.

Manual Organization
===================

Folders exist for individual manuals as follows:

* bitbake-user-manual - The BitBake User Manual

Each folder is self-contained regarding content and figures.

If you want to find HTML versions of the BitBake manuals on the web,
go to http://www.openembedded.org/wiki/Documentation.

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 BitBake User Manual.
The DOC variable specifies the manual you are making:

$ make DOC=bitbake-user-manual

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

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