From: Ilya Maximets <i.maximets@samsung.com>
To: dev@dpdk.org, Declan Doherty <declan.doherty@intel.com>
Cc: Heetae Ahn <heetae82.ahn@samsung.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>,
Ilya Maximets <i.maximets@samsung.com>
Subject: [dpdk-dev] [PATCH] app: don't try to build test-crypto-perf if cryptodev disabled
Date: Mon, 10 Apr 2017 11:14:19 +0300 [thread overview]
Message-ID: <1491812059-2028-1-git-send-email-i.maximets@samsung.com> (raw)
In-Reply-To: <CGME20170410081425eucas1p24667f00bc981db49558c1ba8dd1d9abe@eucas1p2.samsung.com>
This fixes build in following configuration:
CONFIG_RTE_LIBRTE_CRYPTODEV=n
CONFIG_RTE_APP_CRYPTO_PERF=y
Fixes: f8be1786b1b8 ("app/crypto-perf: introduce performance test application")
Signed-off-by: Ilya Maximets <i.maximets@samsung.com>
---
app/Makefile | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/app/Makefile b/app/Makefile
index 4b3a448..c3aeebf 100644
--- a/app/Makefile
+++ b/app/Makefile
@@ -32,8 +32,11 @@
include $(RTE_SDK)/mk/rte.vars.mk
DIRS-$(CONFIG_RTE_TEST_PMD) += test-pmd
-DIRS-$(CONFIG_RTE_APP_CRYPTO_PERF) += test-crypto-perf
DIRS-$(CONFIG_RTE_EXEC_ENV_LINUXAPP) += proc_info
DIRS-$(CONFIG_RTE_LIBRTE_PDUMP) += pdump
+ifeq ($(CONFIG_RTE_LIBRTE_CRYPTODEV),y)
+DIRS-$(CONFIG_RTE_APP_CRYPTO_PERF) += test-crypto-perf
+endif
+
include $(RTE_SDK)/mk/rte.subdir.mk
--
2.7.4
next parent reply other threads:[~2017-04-10 8:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170410081425eucas1p24667f00bc981db49558c1ba8dd1d9abe@eucas1p2.samsung.com>
2017-04-10 8:14 ` Ilya Maximets [this message]
2017-04-10 9:51 ` De Lara Guarch, Pablo
2017-04-10 10:01 ` 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=1491812059-2028-1-git-send-email-i.maximets@samsung.com \
--to=i.maximets@samsung.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=heetae82.ahn@samsung.com \
--cc=thomas.monjalon@6wind.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 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).