From: Tom Rini <trini@konsulko.com>
To: Simon Glass <sjg@chromium.org>
Cc: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
Maxim Cournoyer <maxim.cournoyer@savoirfairelinux.com>,
u-boot@lists.denx.de
Subject: Re: [PATCH 1/1] doc: building documentation
Date: Fri, 30 Dec 2022 13:12:10 -0500 [thread overview]
Message-ID: <20221230181210.GE3787616@bill-the-cat> (raw)
In-Reply-To: <CAPnjgZ3GibWLvuFMYFftfPBxTAPpudKkTGSehGwVC6+L7rKk7A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2163 bytes --]
On Fri, Dec 30, 2022 at 11:51:15AM -0600, Simon Glass wrote:
> Hi Heinrich,
>
> On Thu, 29 Dec 2022 at 22:08, Heinrich Schuchardt
> <heinrich.schuchardt@canonical.com> wrote:
> >
> > Provide a man-page describing how to build the U-Boot documentation.
> >
> > Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
> > ---
> > doc/build/documentation.rst | 90 +++++++++++++++++++++++++++++++++++++
> > doc/build/index.rst | 1 +
> > 2 files changed, 91 insertions(+)
> > create mode 100644 doc/build/documentation.rst
> >
> > diff --git a/doc/build/documentation.rst b/doc/build/documentation.rst
> > new file mode 100644
> > index 0000000000..896264dd7c
> > --- /dev/null
> > +++ b/doc/build/documentation.rst
> > @@ -0,0 +1,90 @@
> > +.. SPDX-License-Identifier: GPL-2.0+:
> > +
> > +Building documentation
> > +======================
> > +
> > +The U-Boot documentation is based on the Sphinx documentation generator.
> > +
> > +HTML documentation
> > +------------------
> > +
> > +The *htmldocs* target is used to build the HTML documentation. It uses the
> > +`Read the Docs Sphinx theme <https://sphinx-rtd-theme.readthedocs.io/en/stable/>`_.
> > +
> > +.. code-block:: bash
> > +
> > + # Create Python environment 'myenv'
> > + python3 -m venv myenv
> > + # Activate the Python environment
> > + . myenv/bin/activate
> > + # Install build requirements
> > + python3 -m pip install -r doc/sphinx/requirements.txt
> > + # Build the documentation
> > + make htmldocs
> > + # Deactivate the Python environment
> > + deactivate
> > + # Display the documentation in a graphical web browser
> > + x-www-browser doc/output/index.html
>
> If this is necessary then it is a bit of a sad indictment on Python. I
> would use:
>
> pip3 install -r doc/sphinx/requirements.txt
> make htmldocs
Which part, exactly? Using a virtual environment is I believe a normal
best practice and "python3 -m pip" rather than "pip3" I assume is
another best practice for portability. Then maybe the final step should
say "Review" not "Display" ?
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-12-30 18:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 4:07 [PATCH 1/1] doc: building documentation Heinrich Schuchardt
2022-12-30 17:51 ` Simon Glass
2022-12-30 18:12 ` Tom Rini [this message]
2022-12-30 18:31 ` Heinrich Schuchardt
2022-12-30 19:02 ` Simon Glass
2022-12-30 19:08 ` Tom Rini
2022-12-30 19:08 ` Heinrich Schuchardt
2023-01-07 18:55 ` Simon Glass
2023-01-07 19:09 ` Tom Rini
2023-01-07 22:16 ` Heinrich Schuchardt
2023-01-07 22:54 ` Simon Glass
2023-01-08 0:11 ` Heinrich Schuchardt
2023-01-08 2:37 ` Simon Glass
2023-01-08 13:44 ` Tom Rini
2023-01-08 15:05 ` Simon Glass
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221230181210.GE3787616@bill-the-cat \
--to=trini@konsulko.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=maxim.cournoyer@savoirfairelinux.com \
--cc=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox