DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, aconole@redhat.com, ruifeng.wang@arm.com,
	david.marchand@redhat.com
Subject: Re: [dpdk-dev] [RFC PATCH] ci: reduce examples built for static builds
Date: Wed, 18 Mar 2020 09:45:11 +0000	[thread overview]
Message-ID: <20200318094511.GB1491@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <3483262.VQhiAETyHQ@xps>

On Mon, Mar 16, 2020 at 07:37:01PM +0100, Thomas Monjalon wrote:
> 16/03/2020 18:09, Bruce Richardson:
> > Static builds can take a lot of space, so reduce the number of examples
> > built when doing those static builds.
> > 
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> > ---
> > --- a/.ci/linux-build.sh
> > +++ b/.ci/linux-build.sh
> > +if [ "$DEF_LIB" = "static" ] ; then
> > +    OPTS="$OPTS -Dexamples=l2fwd,l3fwd"
> > +else
> > +    OPTS="$OPTS -Dexamples=all"
> > +fi
> 
> I was thinking about doing this kind of change in devtools/test-meson-builds.sh
> What do you think?
> 

No major objection. It's probably less likely to be an issue for people
running their own test-builds, though if it saves time and space and
doesn't much affect the number of issues we are going to hit/miss, I don't
see why not do so.

  reply	other threads:[~2020-03-18  9:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-16 17:09 Bruce Richardson
2020-03-16 17:36 ` Aaron Conole
2020-03-17 10:44   ` David Marchand
2020-03-17 12:48     ` Aaron Conole
2020-03-16 18:37 ` Thomas Monjalon
2020-03-18  9:45   ` Bruce Richardson [this message]
2020-04-17 21:58 ` 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=20200318094511.GB1491@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=aconole@redhat.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ruifeng.wang@arm.com \
    --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).