summaryrefslogtreecommitdiffstats
path: root/documentation/README
diff options
context:
space:
mode:
authorMichael Opdenacker <michael.opdenacker@bootlin.com>2023-09-20 06:09:24 +0200
committerSteve Sakoman <steve@sakoman.com>2023-09-23 05:26:16 -1000
commit31af34e1afd678da3b98f3ea46b5c6a4f4e70f35 (patch)
treef412d3af10deb588a383d162c72221a96da51a84 /documentation/README
parenta2de040a4455dd4623d83b0809d14aefbbdac3cb (diff)
downloadpoky-31af34e1afd678da3b98f3ea46b5c6a4f4e70f35.tar.gz
documentation/README: align with master
(From yocto-docs rev: 8638eadda09e932534eb6bb345b4d0299974b219) Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com> Signed-off-by: Steve Sakoman <steve@sakoman.com>
Diffstat (limited to 'documentation/README')
-rw-r--r--documentation/README43
1 files changed, 35 insertions, 8 deletions
diff --git a/documentation/README b/documentation/README
index 6f6a8ec842..4d31036e69 100644
--- a/documentation/README
+++ b/documentation/README
@@ -34,16 +34,18 @@ Manual Organization
34 34
35Here the folders corresponding to individual manuals: 35Here the folders corresponding to individual manuals:
36 36
37* brief-yoctoprojectqs - Yocto Project Quick Start
37* overview-manual - Yocto Project Overview and Concepts Manual 38* overview-manual - Yocto Project Overview and Concepts Manual
38* sdk-manual - Yocto Project Software Development Kit (SDK) Developer's Guide. 39* contributor-guide - Yocto Project and OpenEmbedded Contributor Guide
40* ref-manual - Yocto Project Reference Manual
39* bsp-guide - Yocto Project Board Support Package (BSP) Developer's Guide 41* bsp-guide - Yocto Project Board Support Package (BSP) Developer's Guide
40* dev-manual - Yocto Project Development Tasks Manual 42* dev-manual - Yocto Project Development Tasks Manual
41* kernel-dev - Yocto Project Linux Kernel Development Manual 43* kernel-dev - Yocto Project Linux Kernel Development Manual
42* ref-manual - Yocto Project Reference Manual
43* brief-yoctoprojectqs - Yocto Project Quick Start
44* profile-manual - Yocto Project Profiling and Tracing Manual 44* profile-manual - Yocto Project Profiling and Tracing Manual
45* sdk-manual - Yocto Project Software Development Kit (SDK) Developer's Guide.
45* toaster-manual - Toaster User Manual 46* toaster-manual - Toaster User Manual
46* test-manual - Yocto Project Test Environment Manual 47* test-manual - Yocto Project Test Environment Manual
48* migration-guides - Yocto Project Release and Migration Notes
47 49
48Each folder is self-contained regarding content and figures. 50Each folder is self-contained regarding content and figures.
49 51
@@ -129,6 +131,10 @@ Also install the "inkscape" package from your distribution.
129Inkscape is need to convert SVG graphics to PNG (for EPUB 131Inkscape is need to convert SVG graphics to PNG (for EPUB
130export) and to PDF (for PDF export). 132export) and to PDF (for PDF export).
131 133
134Additionally install "fncychap.sty" TeX font if you want to build PDFs. Debian
135and Ubuntu have it in "texlive-latex-extra" package while RedHat distributions
136and OpenSUSE have it in "texlive-fncychap" package for example.
137
132To build the documentation locally, run: 138To build the documentation locally, run:
133 139
134 $ cd documentation 140 $ cd documentation
@@ -271,6 +277,19 @@ websites.
271More information can be found here: 277More information can be found here:
272https://sublime-and-sphinx-guide.readthedocs.io/en/latest/references.html. 278https://sublime-and-sphinx-guide.readthedocs.io/en/latest/references.html.
273 279
280For external links, we use this syntax:
281`link text <link URL>`__
282
283instead of:
284`link text <link URL>`_
285
286Both syntaxes work, but the latter also creates a "link text" reference
287target which could conflict with other references with the same name.
288So, only use this variant when you wish to make multiple references
289to this link, reusing only the target name.
290
291See https://stackoverflow.com/questions/27420317/restructured-text-rst-http-links-underscore-vs-use
292
274Anchor (<#link>) links are forbidden as they are not checked by Sphinx during 293Anchor (<#link>) links are forbidden as they are not checked by Sphinx during
275the build and may be broken without knowing about it. 294the build and may be broken without knowing about it.
276 295
@@ -340,13 +359,16 @@ The sphinx.ext.intersphinx extension is enabled by default
340so that we can cross reference content from other Sphinx based 359so that we can cross reference content from other Sphinx based
341documentation projects, such as the BitBake manual. 360documentation projects, such as the BitBake manual.
342 361
343References to the BitBake manual can be done: 362References to the BitBake manual can directly be done:
344 - With a specific description instead of the section name: 363 - With a specific description instead of the section name:
345 :ref:`Azure Storage fetcher (az://) <bitbake:bitbake-user-manual/bitbake-user-manual-fetching:fetchers>` 364 :ref:`Azure Storage fetcher (az://) <bitbake-user-manual/bitbake-user-manual-fetching:fetchers>`
346 - With the section name: 365 - With the section name:
347 :ref:`bitbake:bitbake-user-manual/bitbake-user-manual-intro:usage and syntax` option 366 :ref:`bitbake-user-manual/bitbake-user-manual-intro:usage and syntax` option
348 - Linking to the entire BitBake manual: 367
349 :doc:`BitBake User Manual <bitbake:index>` 368If you want to refer to an entire document (or chapter) in the BitBake manual,
369you have to use the ":doc:" macro with the "bitbake:" prefix:
370 - :doc:`BitBake User Manual <bitbake:index>`
371 - :doc:`bitbake:bitbake-user-manual/bitbake-user-manual-metadata`" chapter
350 372
351Note that a reference to a variable (:term:`VARIABLE`) automatically points to 373Note that a reference to a variable (:term:`VARIABLE`) automatically points to
352the BitBake manual if the variable is not described in the Reference Manual's Variable Glossary. 374the BitBake manual if the variable is not described in the Reference Manual's Variable Glossary.
@@ -355,6 +377,11 @@ BitBake manual as follows:
355 377
356 :term:`bitbake:BB_NUMBER_PARSE_THREADS` 378 :term:`bitbake:BB_NUMBER_PARSE_THREADS`
357 379
380This would be the same if we had identical document filenames in
381both the Yocto Project and BitBake manuals:
382
383 :ref:`bitbake:directory/file:section title`
384
358Submitting documentation changes 385Submitting documentation changes
359================================ 386================================
360 387