From: Stephen Hemminger <stephen@networkplumber.org>
To: Shahaf Shuler <shahafs@mellanox.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Bruce Richardson <bruce.richardson@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Mlx meson build
Date: Thu, 14 Jun 2018 08:54:44 -0700 [thread overview]
Message-ID: <20180614085444.3f2b5d21@xeon-e3> (raw)
In-Reply-To: <DB7PR05MB44267AF47BD2E7532461938CC37D0@DB7PR05MB4426.eurprd05.prod.outlook.com>
On Thu, 14 Jun 2018 11:05:23 +0000
Shahaf Shuler <shahafs@mellanox.com> wrote:
> Thursday, June 14, 2018 11:35 AM, Thomas Monjalon :
> > Subject: Re: Mlx meson build
> >
> > 14/06/2018 10:15, Bruce Richardson:
> > > On Wed, Jun 13, 2018 at 03:14:16PM -0700, Stephen Hemminger wrote:
> > > > Is there any chance of getting MLX drivers to build with meson?
> > > > It seems like it should be possible to always build with meson if rdma-
> > core is present.
> > > > The meson build language has ways of checking for necessary
> > dependencies.
> > > >
> > > > Are you working on it for 18.08? or shall I bodge something together.
> > >
> > > I'm not actively working on it, due to time constraints but I'm happy
> > > enough to review and help out others with the work.
> >
> > Same for me. I would be happy to work on it but I cannot commit as I am
> > already very busy for this month.
>
> Currently it is not in the plan for 18.08, we hope to get it in 18.11.
> Besides of it being simpler to write make files and faster to compile is there urgent need from your side?
It is one of the pieces missing to do full meson cut over in 18.11.
Ran into it while trying to do faster builds for testing.
prev parent reply other threads:[~2018-06-14 15:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 22:14 Stephen Hemminger
2018-06-14 8:15 ` Bruce Richardson
2018-06-14 8:35 ` Thomas Monjalon
2018-06-14 11:05 ` Shahaf Shuler
2018-06-14 15:54 ` Stephen Hemminger [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=20180614085444.3f2b5d21@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=shahafs@mellanox.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).