From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-dev] [PATCH] build: print out dependency names for clarity
Date: Thu, 19 Sep 2019 16:07:55 +0100 [thread overview]
Message-ID: <20190919150755.28018-1-bruce.richardson@intel.com> (raw)
To help developers to get the correct dependency name e.g. when creating a
new example that depends on a specific component, print out the dependency
name for each lib/driver as it is processed.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
drivers/meson.build | 3 +++
lib/meson.build | 6 ++++--
2 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/meson.build b/drivers/meson.build
index 2ed2e9541..c3f52d785 100644
--- a/drivers/meson.build
+++ b/drivers/meson.build
@@ -157,6 +157,9 @@ foreach class:dpdk_driver_classes
set_variable('shared_@0@'.format(lib_name), shared_dep)
set_variable('static_@0@'.format(lib_name), static_dep)
+ dependency_name = ''.join(lib_name.split('rte_'))
+ message('drivers/@0@: Defining dependency "@1@"'.format(
+ drv_path, dependency_name))
endif # build
endforeach
diff --git a/lib/meson.build b/lib/meson.build
index e5ff83893..766d3b08e 100644
--- a/lib/meson.build
+++ b/lib/meson.build
@@ -154,7 +154,9 @@ foreach l:libraries
dpdk_static_libraries = [static_lib] + dpdk_static_libraries
endif # sources.length() > 0
- set_variable('shared_' + libname, shared_dep)
- set_variable('static_' + libname, static_dep)
+ set_variable('shared_rte_' + name, shared_dep)
+ set_variable('static_rte_' + name, static_dep)
+ message('lib/@0@: Defining dependency "@1@"'.format(
+ dir_name, name))
endif # if build
endforeach
--
2.21.0
next reply other threads:[~2019-09-19 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 15:07 Bruce Richardson [this message]
2019-10-18 16:54 ` Burakov, Anatoly
2019-10-23 14:40 ` Thomas Monjalon
2019-10-23 15:12 ` Bruce Richardson
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=20190919150755.28018-1-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
/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).