From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>, Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH] devtools: reduce examples in static builds
Date: Sun, 19 Apr 2020 16:29:52 +0200 [thread overview]
Message-ID: <3210362.Bm8zEkEi59@thomas> (raw)
In-Reply-To: <CAJFAV8wfVYS0PZD11=OpbnCODxLXBHjqnMOyvD1HAoigx+GWaw@mail.gmail.com>
19/04/2020 09:08, David Marchand:
> On Sat, Apr 18, 2020 at 3:20 PM Thomas Monjalon <thomas@monjalon.net> wrote:
> > --- a/devtools/test-meson-builds.sh
> > +++ b/devtools/test-meson-builds.sh
> > - options="$options --werror -Dexamples=all"
> > + options="$options --werror"
> > + if echo $* | grep -qw -- '--default-library=static' ; then
> > + options="$options -Dexamples=l3fwd"
> > + else
> > + options="$options -Dexamples=all"
> > + fi
>
> Ok, this is hypothetical, but this would not work when no
> default-library option is passed (static is the default value).
No, with meson, shared is the default:
https://mesonbuild.com/Builtin-options.html#core-options
> How about inverting the check and look for default-library=shared ?
>
> Besides, you won't catch already configured directories.
> While for make environments, this change will have an effect right away.
Yes, I think it is OK to keep old configuration in meson builds
until the build directories are trashed.
next prev parent reply other threads:[~2020-04-19 14:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-18 13:19 Thomas Monjalon
2020-04-19 7:08 ` David Marchand
2020-04-19 14:29 ` Thomas Monjalon [this message]
2020-04-19 14:40 ` Thomas Monjalon
2020-04-21 0:30 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2020-04-21 6:59 ` David Marchand
2020-04-21 9:18 ` 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=3210362.Bm8zEkEi59@thomas \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@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).