Lines Matching +full:build +full:- +full:docs

5 …in the state of “I want to write documentation and get it added to LLVM’s docs” and help them star…
15 .. _`reStructuredText`: http://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html
16 .. _`Sphinx`: http://www.sphinx-doc.org
21 …docs/SphinxQuickstartTemplate.rst``. To use it as a template, make a copy and open it in a text ed…
30 plain-text conventions so it should be quite natural. A basic knowledge of
36 Sphinx's output, see ``docs/README.txt`` for information. Once you have finished with the content, …
37 llvm-commits for review.
40 ---------------------
50 A standard best practice is to make your articles task-oriented. You generally should not be writin…
54 When creating a task-oriented article, follow existing LLVM articles by giving it a filename that s…
66 structure. Use the same kind of adornments (e.g. ``======`` vs. ``------``)
71 -------------------------
75 .. _`reStructuredText Primer`: http://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.ht…
116 .. code-block:: c++
122 For a shell session, use a ``console`` code block (some existing docs use
125 .. code-block:: console
128    $ rm -rf /
132 .. code-block:: llvm
143 .. _`full list`: http://pygments.org/docs/lexers/
173 `build tools <GettingStarted.html>`_
175 using the following command inside the ``llvm-project`` checkout:
177 .. code-block:: console
179    pip install --user -r ./llvm/docs/requirements.txt
181 Then run cmake to build the documentation inside the ``llvm-project`` checkout:
183 .. code-block:: console
185    mkdir build
186    cd build
187    cmake -DLLVM_ENABLE_SPHINX=On ../llvm
188    cmake --build . --target docs-llvm-html
190 In case you already have the Cmake build set up and want to reuse that,
193 After that you find the generated documentation in ``build/docs/html``