From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>, "web@dpdk.org" <web@dpdk.org>
Subject: Re: [dpdk-web] [PATCH] update quick start page
Date: Thu, 18 Jun 2020 08:21:13 +0000 [thread overview]
Message-ID: <59AF69C657FD0841A61C55336867B5B0976930D6@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <20200617203700.3576668-1-thomas@monjalon.net>
> -----Original Message-----
> From: web <web-bounces@dpdk.org> On Behalf Of Thomas Monjalon
> Sent: Wednesday, June 17, 2020 9:37 PM
> To: web@dpdk.org
> Subject: [dpdk-web] [PATCH] update quick start page
>
> Use meson instead of make.
> Remove -n EAL option.
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> content/doc/quick-start.md | 20 ++++----------------
> 1 file changed, 4 insertions(+), 16 deletions(-)
>
> diff --git a/content/doc/quick-start.md b/content/doc/quick-start.md index
> fdffa98..1ecc8b8 100644
> --- a/content/doc/quick-start.md
> +++ b/content/doc/quick-start.md
> @@ -11,17 +11,11 @@ Extract sources
> cd dpdk
> ```
>
> -Enable pcap (libpcap headers are required).
> +Build libraries, tests and examples applications.
>
> ```
> - make config T=x86_64-native-linuxapp-gcc
> - sed -ri 's,(PMD_PCAP=).*,\1y,' build/.config -```
> -
> -Build libraries and test application (Linux headers may be needed with
> default config).
> -
> -```
> - make
> + meson -Dexamples=all build
Do we really want building all examples to be part of the default instructions? It will lead to a longer build time?
I think we should give initial instructions just with meson build, and then afterwards show building examples.
next prev parent reply other threads:[~2020-06-18 8:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 20:37 Thomas Monjalon
2020-06-18 8:21 ` Richardson, Bruce [this message]
2020-06-18 8:50 ` Thomas Monjalon
2020-06-18 9:07 ` Richardson, Bruce
2020-06-18 9:59 ` Thomas Monjalon
2020-06-18 10:17 ` Richardson, Bruce
2020-06-18 12:27 ` [dpdk-web] [PATCH v2] " Thomas Monjalon
2020-06-18 12:33 ` Richardson, Bruce
2020-06-22 15:03 ` Thomas Monjalon
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=59AF69C657FD0841A61C55336867B5B0976930D6@IRSMSX103.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=thomas@monjalon.net \
--cc=web@dpdk.org \
/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).