From: Bruce Richardson <bruce.richardson@intel.com>
To: bluca@debian.org, thomas@monjalon.net
Cc: dev@dpdk.org, john.mcnamara@intel.com,
Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-dev] [PATCH 04/10] drivers/common: add reasons for components being disabled
Date: Wed, 5 Jun 2019 21:22:42 +0100 [thread overview]
Message-ID: <20190605202248.394-5-bruce.richardson@intel.com> (raw)
In-Reply-To: <20190605202248.394-1-bruce.richardson@intel.com>
For each driver where we optionally disable it, add in the reason why it's
being disabled, so the user knows how to fix it.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
drivers/common/dpaax/meson.build | 3 ++-
drivers/common/mvep/meson.build | 1 +
drivers/common/qat/meson.build | 1 +
3 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/common/dpaax/meson.build b/drivers/common/dpaax/meson.build
index 78378e2a6..a315e7786 100644
--- a/drivers/common/dpaax/meson.build
+++ b/drivers/common/dpaax/meson.build
@@ -4,7 +4,8 @@
allow_experimental_apis = true
if not is_linux
- build = false
+ build = false
+ reason = 'only supported on linux'
endif
sources = files('dpaax_iova_table.c')
diff --git a/drivers/common/mvep/meson.build b/drivers/common/mvep/meson.build
index 8ccfacb3f..8df4bc6e0 100644
--- a/drivers/common/mvep/meson.build
+++ b/drivers/common/mvep/meson.build
@@ -10,6 +10,7 @@ inc_dir = path + '/include'
lib = cc.find_library('libmusdk', dirs: [lib_dir], required: false)
if not lib.found()
build = false
+ reason = 'missing dependency, "libmusdk"'
else
ext_deps += lib
includes += include_directories(inc_dir)
diff --git a/drivers/common/qat/meson.build b/drivers/common/qat/meson.build
index 80b6b25a8..8de249289 100644
--- a/drivers/common/qat/meson.build
+++ b/drivers/common/qat/meson.build
@@ -4,6 +4,7 @@
# This does not build a driver, but instead holds common files for
# the crypto and compression drivers.
build = false
+reason = '' # sentinal value to suppress printout
qat_deps = ['bus_pci']
qat_sources = files('qat_common.c',
'qat_qp.c',
--
2.21.0
next prev parent reply other threads:[~2019-06-05 20:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 20:22 [dpdk-dev] [PATCH 00/10] enhance meson summary - list disabled components Bruce Richardson
2019-06-05 20:22 ` [dpdk-dev] [PATCH 01/10] build: print list of disabled components for meson build Bruce Richardson
2019-06-05 20:22 ` [dpdk-dev] [PATCH 02/10] lib: add reasons for components being disabled Bruce Richardson
2019-06-05 20:22 ` [dpdk-dev] [PATCH 03/10] drivers/bus: " Bruce Richardson
2019-06-05 20:22 ` Bruce Richardson [this message]
2019-06-05 20:22 ` [dpdk-dev] [PATCH 05/10] drivers/compress: " Bruce Richardson
2019-06-05 20:22 ` [dpdk-dev] [PATCH 06/10] drivers/crypto: " Bruce Richardson
2019-06-05 20:22 ` [dpdk-dev] [PATCH 07/10] drivers/event: " Bruce Richardson
2019-06-05 20:22 ` [dpdk-dev] [PATCH 08/10] drivers/mempool: " Bruce Richardson
2019-06-05 20:22 ` [dpdk-dev] [PATCH 09/10] drivers/net: " Bruce Richardson
2019-06-05 20:22 ` [dpdk-dev] [PATCH 10/10] drivers/raw: " Bruce Richardson
2019-06-05 20:39 ` [dpdk-dev] [PATCH 00/10] enhance meson summary - list disabled components Luca Boccassi
2019-06-18 13:18 ` Bruce Richardson
2019-07-02 21:21 ` 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=20190605202248.394-5-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.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).