From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [ptxdist] [PATCH] doc: including_bsp_doc: add missing venv creation command
Date: Tue, 16 Oct 2018 09:47:06 +0200 [thread overview]
Message-ID: <20181016074706.o7ch4yq3yfehzmfl@pengutronix.de> (raw)
In-Reply-To: <20181010121012.20978-1-a.fatoum@pengutronix.de>
On Wed, Oct 10, 2018 at 02:10:12PM +0200, Ahmad Fatoum wrote:
> otherwise, there wouldn't be an env/ directory to source inside.
>
> Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
> ---
> doc/including_bsp_doc.inc | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/doc/including_bsp_doc.inc b/doc/including_bsp_doc.inc
> index cfccc45b4e80..e6c6bb6f7ded 100644
> --- a/doc/including_bsp_doc.inc
> +++ b/doc/including_bsp_doc.inc
> @@ -32,6 +32,7 @@ when not globally present in the host system.
> .. code-block:: text
>
> $ pip3 install --upgrade --user pip virtualenv
Hmm, ist virtualenv still needed in this case?
Michael
> + $ python3 -mvenv env
> $ source env/bin/activate
> $ pip3 install sphinx
> $ pip3 install sphinx_rtd_theme
> --
> 2.19.0
>
>
> _______________________________________________
> ptxdist mailing list
> ptxdist@pengutronix.de
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2018-10-16 7:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 12:10 Ahmad Fatoum
2018-10-16 7:47 ` Michael Olbrich [this message]
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=20181016074706.o7ch4yq3yfehzmfl@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=ptxdist@pengutronix.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