From: Bruce Richardson <bruce.richardson@intel.com>
To: Luca Boccassi <bluca@debian.org>
Cc: dev@dpdk.org, thomas@monjalon.net, mb@smartsharesystems.com,
techboard@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/3] RFC: Support disabling DPDK drivers in meson builds
Date: Thu, 26 Sep 2019 09:33:45 +0100 [thread overview]
Message-ID: <20190926083345.GB1821@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <bae70ffc944302fa4b527817d75a219fdce5c013.camel@debian.org>
On Wed, Sep 25, 2019 at 07:01:10PM +0100, Luca Boccassi wrote:
> On Wed, 2019-09-25 at 15:55 +0100, Bruce Richardson wrote:
> > Following on from the discussion about meson at userspace 2019, here
> > is
> > a patchset which allows a user to disable drivers in a DPDK build.
> > This
> > set also includes the changes necessary to recursively disable any
> > drivers that depend upon the disabled one, e.g. disabling
> > mempool/dpaa
> > also disables net/dpaa and event/dpaa with suitable reasons provided
> > in
> > the output summary at the end of the meson configuration phase.
> >
> > A number of changes are made to the lib/meson.build file too, in
> > order
> > to keep the general logic flow between drivers/meson.build and
> > lib/meson.build as similar as possible.
> >
> > Example of use:
> >
> > meson -Ddisable_drivers=mempool/dpaa,net/i40e build
> >
> > Bruce Richardson (3):
> > build: align variable names between drivers and libs
> > build: process dependencies before main build check
> > build: support disabling drivers with meson
> >
> > drivers/meson.build | 45 +++++++++++++++++++++++++++--------------
> > ----
> > lib/meson.build | 23 +++++++++++++----------
> > meson_options.txt | 2 ++
> > 3 files changed, 42 insertions(+), 28 deletions(-)
>
> Series-grumbly-acked-by: Luca Boccassi <bluca@debian.org>
>
Not exactly doing my happy-dance here myself about this set, but I think
it's something those building their own DPDK will appreciate.
next prev parent reply other threads:[~2019-09-26 8:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 14:55 Bruce Richardson
2019-09-25 14:55 ` [dpdk-dev] [PATCH 1/3] build: align variable names between drivers and libs Bruce Richardson
2019-09-25 14:55 ` [dpdk-dev] [PATCH 2/3] build: process dependencies before main build check Bruce Richardson
2019-09-25 14:55 ` [dpdk-dev] [PATCH 3/3] build: support disabling drivers with meson Bruce Richardson
2022-01-06 8:23 ` Morten Brørup
2022-01-06 9:48 ` Thomas Monjalon
2022-01-06 10:10 ` Morten Brørup
2022-01-07 13:42 ` Bruce Richardson
2019-09-25 18:01 ` [dpdk-dev] [PATCH 0/3] RFC: Support disabling DPDK drivers in meson builds Luca Boccassi
2019-09-26 8:33 ` Bruce Richardson [this message]
2019-09-26 15:28 ` Morten Brørup
2019-10-23 21:24 ` Thomas Monjalon
2019-09-27 7:14 ` [dpdk-dev] [dpdk-techboard] " Maxime Coquelin
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=20190926083345.GB1821@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
--cc=techboard@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).