DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 1/3] app/cmdline_test: fix build without app/test
Date: Mon, 18 Nov 2013 23:31:00 +0100	[thread overview]
Message-ID: <5b5f0bdcc20741f370901dff4267dc45f0a8ae44.1384813681.git.thomas.monjalon@6wind.com> (raw)
In-Reply-To: <cover.1384813680.git.thomas.monjalon@6wind.com>
In-Reply-To: <cover.1384813680.git.thomas.monjalon@6wind.com>

This application is built if LIBRTE_CMDLINE is enabled.
But there was no enabled source file if APP_TEST is disabled.
Let's consider that CONFIG_RTE_APP_TEST apply only on app/test.

Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
---
 app/cmdline_test/Makefile |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/app/cmdline_test/Makefile b/app/cmdline_test/Makefile
index 00b398c..dab678a 100644
--- a/app/cmdline_test/Makefile
+++ b/app/cmdline_test/Makefile
@@ -39,8 +39,8 @@ APP = cmdline_test
 #
 # all sources are stored in SRCS-y
 #
-SRCS-$(CONFIG_RTE_APP_TEST) += cmdline_test.c
-SRCS-$(CONFIG_RTE_APP_TEST) += commands.c
+SRCS-$(CONFIG_RTE_LIBRTE_CMDLINE) += cmdline_test.c
+SRCS-$(CONFIG_RTE_LIBRTE_CMDLINE) += commands.c
 
 CFLAGS += -O3
 CFLAGS += $(WERROR_FLAGS)
-- 
1.7.10.4

  reply	other threads:[~2013-11-18 22:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 22:30 [dpdk-dev] [PATCH 0/3] app: fix build Thomas Monjalon
2013-11-18 22:31 ` Thomas Monjalon [this message]
2013-11-18 22:31 ` [dpdk-dev] [PATCH 2/3] app/testpmd: fix build without librte_cmdline Thomas Monjalon
2013-11-18 22:31 ` [dpdk-dev] [PATCH 3/3] app/test: " Thomas Monjalon
2013-11-21 14:26 ` [dpdk-dev] [PATCH 0/3] app: fix build Olivier MATZ
2013-11-21 21:09   ` 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=5b5f0bdcc20741f370901dff4267dc45f0a8ae44.1384813681.git.thomas.monjalon@6wind.com \
    --to=thomas.monjalon@6wind.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).