vasilito
cb424d7448
verify-patch-sanity.py validates every active recipe .patch has internally- consistent hunk line counts — catching the 'malformed patch at line N' failure at commit/CI/preflight time instead of hours into a cook. This cycle hit that class three times (qtwaylandscanner, sddm, xwayland), each only discovered when cookbook tried to apply the patch. Running it across the repo found 29 latent malformed patches (validated against GNU patch: e.g. relibc/P3-sysv-ipc reproduces 'malformed patch at line 22'). They were harmless only because they sit in vendored recipes (baked, not re- applied) — but would fail on any version-bump re-derivation. --fix recounts the hunk headers (body untouched) and repaired all 29. Wired into build-preflight.sh (Phase 1.0D) and redbear-ci.yml, with a unit test (test-patch-sanity.sh). Skips archived/legacy trees and unvalidatable formats (empty placeholders, bare-@@ git hunks).
70 lines
2.5 KiB
Plaintext
70 lines
2.5 KiB
Plaintext
LLVM Documentation
|
|
==================
|
|
|
|
LLVM's documentation is written in reStructuredText, a lightweight
|
|
plaintext markup language (file extension `.rst`). While the
|
|
reStructuredText documentation should be quite readable in source form, it
|
|
is mostly meant to be processed by the Sphinx documentation generation
|
|
system to create HTML pages which are hosted on <https://llvm.org/docs/> and
|
|
updated after every commit. Manpage output is also supported, see below.
|
|
|
|
If you instead would like to generate and view the HTML locally, install
|
|
Sphinx <http://sphinx-doc.org/> and then do:
|
|
|
|
cd <build-dir>
|
|
cmake -DLLVM_ENABLE_SPHINX=true -DSPHINX_OUTPUT_HTML=true <src-dir>
|
|
make -j3 docs-llvm-html
|
|
$BROWSER <build-dir>/docs/html/index.html
|
|
|
|
The mapping between reStructuredText files and generated documentation is
|
|
`docs/Foo.rst` <-> `<build-dir>/docs//html/Foo.html` <-> `https://llvm.org/docs/Foo.html`.
|
|
|
|
If you are interested in writing new documentation, you will want to read
|
|
`SphinxQuickstartTemplate.rst` which will get you writing documentation
|
|
very fast and includes examples of the most important reStructuredText
|
|
markup syntax.
|
|
|
|
Manpage Output
|
|
===============
|
|
|
|
Building the manpages is similar to building the HTML documentation. The
|
|
primary difference is to use the `man` makefile target, instead of the
|
|
default (which is `html`). Sphinx then produces the man pages in the
|
|
directory `<build-dir>/docs/man/`.
|
|
|
|
cd <build-dir>
|
|
cmake -DLLVM_ENABLE_SPHINX=true -DSPHINX_OUTPUT_MAN=true <src-dir>
|
|
make -j3 docs-llvm-man
|
|
man -l <build-dir>/docs/man/FileCheck.1
|
|
|
|
The correspondence between .rst files and man pages is
|
|
`docs/CommandGuide/Foo.rst` <-> `<build-dir>/docs//man/Foo.1`.
|
|
These .rst files are also included during HTML generation so they are also
|
|
viewable online (as noted above) at e.g.
|
|
`https://llvm.org/docs/CommandGuide/Foo.html`.
|
|
|
|
Checking links
|
|
==============
|
|
|
|
The reachability of external links in the documentation can be checked by
|
|
running:
|
|
|
|
cd llvm/docs/
|
|
sphinx-build -b linkcheck . _build/lintcheck/
|
|
# report will be generated in _build/lintcheck/output.txt
|
|
|
|
Doxygen page Output
|
|
==============
|
|
|
|
Install doxygen <https://www.doxygen.nl/download.html> and dot2tex <https://dot2tex.readthedocs.io/en/latest>.
|
|
|
|
cd <build-dir>
|
|
cmake -DLLVM_ENABLE_DOXYGEN=On <llvm-top-src-dir>
|
|
make doxygen-llvm # for LLVM docs
|
|
make doxygen-clang # for clang docs
|
|
|
|
It will generate html in
|
|
|
|
<build-dir>/docs/doxygen/html # for LLVM docs
|
|
<build-dir>/tools/clang/docs/doxygen/html # for clang docs
|