From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: bluca@debian.org, dev@dpdk.org
Subject: Re: [dpdk-dev] meson reference guide
Date: Wed, 5 Jun 2019 11:39:37 +0100 [thread overview]
Message-ID: <20190605103937.GB1550@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <15005345.pJipbXyxuh@xps>
On Wed, Jun 05, 2019 at 12:27:34PM +0200, Thomas Monjalon wrote:
> Hi,
>
> For the make build system, we have doc/build-sdk-quick.txt
> which is very short and displayed with "make help" for a quick reference.
>
> For meson, we have doc/build-sdk-meson.txt which is in reality
> a full guide formatted in rst.
> Should it be moved in Sphinx guides?
Probably.
> Do we want a really short guide for the basic commands, including
> runnning the tests or build the doc? with other basic tooling?
>
Yes for a short guide, but not sure I'd include tests and building docs in
it. I'd suggest just starting with the first section alone of the existing
doc. For further docs, links to the online documentation on dpdk.org should
suffice rather than needing instructions on building the docs locally.
/Bruce
prev parent reply other threads:[~2019-06-05 10:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 10:27 Thomas Monjalon
2019-06-05 10:39 ` Bruce Richardson [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=20190605103937.GB1550@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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;
as well as URLs for NNTP newsgroup(s).