From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Subject: Re: [dpdk-dev] Projects depending on make (versus meson)
Date: Tue, 8 Jan 2019 10:55:36 +0000 [thread overview]
Message-ID: <20190108105535.GA17732@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <3581820.WYqOYd8h7C@xps>
On Tue, Jan 08, 2019 at 11:44:03AM +0100, Thomas Monjalon wrote:
> 07/01/2019 19:21, Stephen Hemminger:
> > I recently bumped into NFF-go which probably will have problems with meson build.
> > It puts dpdk and pktgen-dpdk in as git submodules and then builds it all together
> > with Go environment.
>
> You mean they must switch to meson and use DPDK discovery with pkg-config?
> Do you see any blocker?
>
> > The current model is a nuisance because can't get Mellanox drivers for Azure by
> > default.
>
> In the make build system, some libraries (like Mellanox drivers) must be
> explicitly enabled by modifying the .config file before running make.
> There should be a hook in the app build system to allow some tuning.
One thing I've been considering for our meson build system, is possibly
adding in a config option to explicitly request specific drivers to be
built and error out if they cannot be. Right now, it's all based on what is
available - there is no way to tell meson to error out the config if the
dependencies for the Mellanox drivers, or the QAT crypto drivers are
missing.
Thoughts (and patches :-)) welcome.
/Bruce
prev parent reply other threads:[~2019-01-08 10:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 18:21 Stephen Hemminger
2019-01-08 10:44 ` Thomas Monjalon
2019-01-08 10:55 ` Bruce Richardson [this message]
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=20190108105535.GA17732@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).