DPDK patches and discussions
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: dev@dpdk.org
Cc: bruce.richardson@intel.com, thomas@monjalon.net,
	Luca Boccassi <bluca@debian.org>
Subject: [dpdk-dev] [PATCH] build: document that Meson < 0.45 will fail to list private deps
Date: Thu, 15 Nov 2018 18:26:28 +0000	[thread overview]
Message-ID: <20181115182628.8114-1-bluca@debian.org> (raw)

Meson can generate the list of private dependencies of libraries
automatically for the pkgconfig file only since version 0.45.0.

Signed-off-by: Luca Boccassi <bluca@debian.org>
---
 doc/build-sdk-meson.txt | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/doc/build-sdk-meson.txt b/doc/build-sdk-meson.txt
index 508e2cb64..229398bb0 100644
--- a/doc/build-sdk-meson.txt
+++ b/doc/build-sdk-meson.txt
@@ -203,3 +203,9 @@ From examples/helloworld/Makefile::
 
 	build:
 		@mkdir -p $@
+
+NOTE: for --static builds, DPDK needs to be built with Meson >= 0.45 in order to
+fully generate the list of private dependencies. If DPDK is built with an older
+version of Meson, it might be necessary to manually specify dependencies of DPDK
+PMDs/libraries, for example -lmlx5 -lmnl for librte-pmd-mlx5, or the static link
+step might fail.
-- 
2.19.1

             reply	other threads:[~2018-11-15 18:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-15 18:26 Luca Boccassi [this message]
2018-11-16 10:26 ` Bruce Richardson
2018-11-16 10:52   ` Luca Boccassi
2018-11-16 10:55     ` Luca Boccassi
2018-11-16 10:57 ` [dpdk-dev] [PATCH v2] build: document that Meson < 0.46 " Luca Boccassi
2018-11-16 11:47   ` Richardson, Bruce
2018-11-18 23:51     ` 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=20181115182628.8114-1-bluca@debian.org \
    --to=bluca@debian.org \
    --cc=bruce.richardson@intel.com \
    --cc=dev@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).