summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBill Traynor <wmat@alphatroop.com>2013-01-14 15:24:34 -0500
committerRichard Purdie <richard.purdie@linuxfoundation.org>2014-01-13 21:53:22 +0000
commit84e72fa4a9e785e39209fe9d1ffcff540697b6f8 (patch)
tree960b37ba3764dfa59bcb4a2365d458717212f016
parent9a58215e7b246c63329f8c88b6eb71a004641be7 (diff)
downloadbitbake-84e72fa4a9e785e39209fe9d1ffcff540697b6f8.tar.gz
documentation: Add README based off the YP docs one
Reusing the README file from the Yocto Project Documentation directory but removed the YP specific content and changed to be specific to BitBake. Signed-off-by: Bill Traynor <wmat@alphatroop.com>
-rw-r--r--doc/README39
1 files changed, 39 insertions, 0 deletions
diff --git a/doc/README b/doc/README
new file mode 100644
index 000000000..90aafea9c
--- /dev/null
+++ b/doc/README
@@ -0,0 +1,39 @@
+Documentation
+=============
+
+This is the directory that contains the BitBake documentation.
+
+Manual Organization
+===================
+
+Folders exist for individual manuals as follows:
+
+* 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=user-manual
+
+template
+========
+Contains various templates, fonts, and some old PNG files.
+
+tools
+=====
+Contains a tool to convert the DocBook files to PDF format.