mirror of
https://git.yoctoproject.org/poky
synced 2026-09-19 09:49:33 +02:00
bitbake: docs: update README file after migrationg to Sphinx
(Bitbake rev: ec4c481a0c3a3ccd0ef0832f128afdc047876552) Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
committed by
Richard Purdie
parent
25fd9fddc3
commit
ac8257be72
@@ -15,25 +15,41 @@ Each folder is self-contained regarding content and figures.
|
|||||||
If you want to find HTML versions of the BitBake manuals on the web,
|
If you want to find HTML versions of the BitBake manuals on the web,
|
||||||
go to http://www.openembedded.org/wiki/Documentation.
|
go to http://www.openembedded.org/wiki/Documentation.
|
||||||
|
|
||||||
Makefile
|
Sphinx
|
||||||
========
|
======
|
||||||
|
|
||||||
The Makefile processes manual directories to create HTML, PDF,
|
The BitBake documentation was migrated from the original DocBook
|
||||||
tarballs, etc. Details on how the Makefile work are documented
|
format to Sphinx based documentation for the Yocto Project 3.2
|
||||||
inside the Makefile. See that file for more information.
|
release.
|
||||||
|
|
||||||
To build a manual, you run the make command and pass it the name
|
Additional information related to the Sphinx migration, and guidelines
|
||||||
of the folder containing the manual's contents.
|
for developers willing to contribute to the BitBake documentation can
|
||||||
For example, the following command run from the documentation directory
|
be found in the Yocto Project Documentation README file:
|
||||||
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
|
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/tree/documentation/README
|
||||||
|
|
||||||
template
|
How to build the Yocto Project documentation
|
||||||
========
|
============================================
|
||||||
Contains various templates, fonts, and some old PNG files.
|
|
||||||
|
|
||||||
tools
|
Sphinx is written in Python. While it might work with Python2, for
|
||||||
=====
|
obvious reasons, we will only support building the BitBake
|
||||||
Contains a tool to convert the DocBook files to PDF format.
|
documentation with Python3.
|
||||||
|
|
||||||
|
Sphinx might be available in your Linux distro packages repositories,
|
||||||
|
however it is not recommend using distro packages, as they might be
|
||||||
|
old versions, especially if you are using an LTS version of your
|
||||||
|
distro. The recommended method to install Sphinx and all required
|
||||||
|
dependencies is to use the Python Package Index (pip).
|
||||||
|
|
||||||
|
To install all required packages run:
|
||||||
|
|
||||||
|
$ pip3 install sphinx sphinx_rtd_theme pyyaml
|
||||||
|
|
||||||
|
To build the documentation locally, run:
|
||||||
|
|
||||||
|
$ cd documentation
|
||||||
|
$ make -f Makefile.sphinx html
|
||||||
|
|
||||||
|
The resulting HTML index page will be _build/html/index.html, and you
|
||||||
|
can browse your own copy of the locally generated documentation with
|
||||||
|
your browser.
|
||||||
|
|||||||
Reference in New Issue
Block a user