DPDK website maintenance
 help / color / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "web@dpdk.org" <web@dpdk.org>
Subject: Re: [dpdk-web] [PATCH] update quick start page
Date: Thu, 18 Jun 2020 11:59:41 +0200
Message-ID: <5497603.1Gqg1Hbvuo@thomas> (raw)
In-Reply-To: <59AF69C657FD0841A61C55336867B5B09769328B@IRSMSX103.ger.corp.intel.com>

18/06/2020 11:07, Richardson, Bruce:
> From: Thomas Monjalon <thomas@monjalon.net>
> > 18/06/2020 10:21, Richardson, Bruce:
> > > From: Thomas Monjalon
> > > > --- a/content/doc/quick-start.md
> > > > +++ b/content/doc/quick-start.md
> > > > -  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.
> > 
> > How do you suggest is the best to compile examples in a second step?
> > 	meson configure -Dexamples=all ?
> > 
> > 
> 
> No rather than an additional step, I think showing it as an alternative set
> of instructions might work well. Something like:
> 
> """
> To build the DPDK libraries, drivers and test applications use:
> 
> meson build
> ninja -C build
> 
> To include the examples as part of the build, the -Dexamples flag can be
> passed to meson, with a comma-separated list of the desired examples, or
> 'all' to indicate all buildable examples. For example:
> 
> meson -Dexamples=all build
> ninja -C build
> """

I avoid such long sentence in a quick start guide.
What about this?

"
To include the examples as part of the build,
replace the meson command with:

meson -Dexamples=all build
"



  reply index

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
2020-06-18  8:50   ` Thomas Monjalon
2020-06-18  9:07     ` Richardson, Bruce
2020-06-18  9:59       ` Thomas Monjalon [this message]
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 publically 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=5497603.1Gqg1Hbvuo@thomas \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --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

DPDK website maintenance

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/web/0 web/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 web web/ http://inbox.dpdk.org/web \
		web@dpdk.org
	public-inbox-index web


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.web


AGPL code for this site: git clone https://public-inbox.org/ public-inbox