All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Shahaf Shuler <shahafs@mellanox.com>
Cc: yskoh@mellanox.com, matan@mellanox.com,
	nelio.laranjeiro@6wind.com, bluca@debian.org, dev@dpdk.org
Subject: Re: [PATCH v6 1/2] net/mlx5: support meson build
Date: Thu, 13 Sep 2018 13:41:42 +0100	[thread overview]
Message-ID: <20180913124142.GA1776@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <3c634e089dbcc5a6a7fc7cbff91958598f595e57.1536839688.git.shahafs@mellanox.com>

On Thu, Sep 13, 2018 at 03:11:05PM +0300, Shahaf Shuler wrote:
> From: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
> 
> Compile Mellanox driver when its external dependencies are met.  A
> glue version of the driver can still be requested by using the
> -Denable_driver_mlx_glue=true
> 
> To avoid modifying the whole sources and keep the compatibility with
> current build systems (e.g. make), the mlx5_autoconf.h is still
> generated by invoking DPDK scripts though meson's run_command() instead
> of using has_types, has_members, ... commands.
> 

This part of the commit message is no longer accurate.

> Meson will try to find the required external libraries.  When they are
> not installed system wide, they can be provided though CFLAGS, LDFLAGS
> and LD_LIBRARY_PATH environment variables, example (considering
> RDMA-Core is installed in /tmp/rdma-core):
> 
>  # CLFAGS=-I/tmp/rdma-core/build/include \
>    LDFLAGS=-L/tmp/rdma-core/build/lib \
>    LD_LIBRARY_PATH=/tmp/rdma-core/build/lib \
>    meson output
>  # LD_LIBRARY_PATH=/tmp/rdma-core/build/lib \
>    ninja -C output install
> 
> Note: LD_LIBRARY_PATH before ninja is necessary when the meson
> configuration has changed (e.g. meson configure has been called), in
> such situation the LD_LIBRARY_PATH is necessary to invoke the
> autoconfiguration script.
> 
> Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
> Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>

The signoffs should be together, followed by the ack.

Otherwise LGTM (for both patches)

/Bruce

  reply	other threads:[~2018-09-13 12:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Message-Id: <7812af2267017898332783e934bef9478814ae96.1535361299.git.nelio.laranjeiro@6wind.com>
2018-08-27 12:42 ` [PATCH v2] net/mlx: add meson build support Nelio Laranjeiro
2018-08-28 15:45   ` Bruce Richardson
2018-08-29  9:34     ` Nélio Laranjeiro
2018-08-29 10:01       ` Bruce Richardson
2018-08-29 12:44         ` Nélio Laranjeiro
2018-08-29 10:00     ` Luca Boccassi
2018-08-29 11:59       ` Nélio Laranjeiro
2018-08-29 12:28         ` Luca Boccassi
2018-08-31 16:24         ` Luca Boccassi
2018-08-29 13:48   ` [PATCH v3] " Nelio Laranjeiro
2018-08-30 14:46     ` Bruce Richardson
2018-08-31  7:05       ` Nélio Laranjeiro
2018-08-31  7:16     ` [PATCH v4] " Nelio Laranjeiro
2018-09-05 11:47       ` [PATCH v5] " Shahaf Shuler
2018-09-07 10:34         ` Bruce Richardson
2018-09-13  9:22           ` Bruce Richardson
2018-09-13 10:12             ` Shahaf Shuler
2018-09-13 10:51               ` Bruce Richardson
2018-09-13 12:11         ` [PATCH v6 1/2] net/mlx5: support meson build Shahaf Shuler
2018-09-13 12:41           ` Bruce Richardson [this message]
2018-09-16  9:01             ` Shahaf Shuler
2018-09-13 12:11         ` [PATCH v6 2/2] net/mlx4: " Shahaf Shuler
2018-08-27 11:10 [PATCH 1/2] build: add extra cflags ldflags to meson option Nelio Laranjeiro
2018-08-27 11:10 ` [PATCH 2/2] net/mlx: add meson build support Nelio Laranjeiro
2018-08-27 11:24 ` [PATCH 1/2] build: add extra cflags ldflags to meson option Bruce Richardson
2018-08-27 12:20   ` Nélio Laranjeiro

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=20180913124142.GA1776@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=matan@mellanox.com \
    --cc=nelio.laranjeiro@6wind.com \
    --cc=shahafs@mellanox.com \
    --cc=yskoh@mellanox.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.