From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: [dpdk-dev] [RFC] mk: add config items to disable tools and tests
Date: Mon, 25 Jul 2016 18:36:03 +0100 [thread overview]
Message-ID: <1469468163-29814-1-git-send-email-ferruh.yigit@intel.com> (raw)
It is not possible to prevent compiling some tests and tools. These
enabled when a library or specific exec env enabled. This compilation
can be overkill for someone who is compiling DPDK just as library.
Adding two new config options, to completely enable/disable tools and
test. Both enable default, compatible with existing behavior.
This commit also shows app folder is used both for unit tests, test
tools and other tools for DPDK, it is possible to discuss separating
tests into a test folder.
Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
Targeted for DPDK16.11
---
app/Makefile | 5 +++++
config/common_base | 10 ++++++++++
2 files changed, 15 insertions(+)
diff --git a/app/Makefile b/app/Makefile
index 30ec292..76b1c2e 100644
--- a/app/Makefile
+++ b/app/Makefile
@@ -31,12 +31,17 @@
include $(RTE_SDK)/mk/rte.vars.mk
+ifeq ($(CONFIG_RTE_ENABLE_TESTS),y)
DIRS-$(CONFIG_RTE_APP_TEST) += test
DIRS-$(CONFIG_RTE_LIBRTE_ACL) += test-acl
DIRS-$(CONFIG_RTE_LIBRTE_PIPELINE) += test-pipeline
DIRS-$(CONFIG_RTE_TEST_PMD) += test-pmd
DIRS-$(CONFIG_RTE_LIBRTE_CMDLINE) += cmdline_test
+endif
+
+ifeq ($(CONFIG_RTE_ENABLE_TOOLS),y)
DIRS-$(CONFIG_RTE_EXEC_ENV_LINUXAPP) += proc_info
DIRS-$(CONFIG_RTE_LIBRTE_PDUMP) += pdump
+endif
include $(RTE_SDK)/mk/rte.subdir.mk
diff --git a/config/common_base b/config/common_base
index 7830535..50fdf98 100644
--- a/config/common_base
+++ b/config/common_base
@@ -573,6 +573,11 @@ CONFIG_RTE_LIBRTE_XEN_DOM0=n
CONFIG_RTE_INSECURE_FUNCTION_WARNING=n
#
+# Enable/Disable all test applications
+#
+CONFIG_RTE_ENABLE_TESTS=y
+
+#
# Compile the test application
#
CONFIG_RTE_APP_TEST=y
@@ -583,4 +588,9 @@ CONFIG_RTE_APP_TEST_RESOURCE_TAR=n
#
CONFIG_RTE_TEST_PMD=y
CONFIG_RTE_TEST_PMD_RECORD_CORE_CYCLES=n
+
+#
+# Enable/Disable all test applications
+#
+CONFIG_RTE_ENABLE_TOOLS=y
CONFIG_RTE_TEST_PMD_RECORD_BURST_STATS=n
--
2.7.4
reply other threads:[~2016-07-25 17:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1469468163-29814-1-git-send-email-ferruh.yigit@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--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).