From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"thomas.monjalon@6wind.com" <thomas.monjalon@6wind.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH v4] devtools: add tags and cscope index file generation support
Date: Tue, 21 Mar 2017 09:35:22 +0530 [thread overview]
Message-ID: <20170321040521.n7cemveimnkxs5fz@localhost.localdomain> (raw)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D89126527625D3@IRSMSX108.ger.corp.intel.com>
On Mon, Mar 20, 2017 at 10:15:45AM +0000, Dumitrescu, Cristian wrote:
>
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jerin Jacob
> > Sent: Sunday, March 19, 2017 10:52 AM
> > To: dev@dpdk.org
> > Cc: thomas.monjalon@6wind.com; Yigit, Ferruh <ferruh.yigit@intel.com>;
> > Jerin Jacob <jerin.jacob@caviumnetworks.com>
> > Subject: [dpdk-dev] [PATCH v4] devtools: add tags and cscope index file
> > generation support
> >
> > This script generates cscope, gtags, and tags index files based on
> > EAL environment(architecture and OS(linux/bsd)).
> >
> > If EAL environment(config) is not specified, the script generates tag
> > files based on available source code.
> >
> > Usage: build-tags.sh [-h] [-v] tags|cscope|gtags|etags [config]
> >
> > example usage:
> > ./devtools/build-tags.sh cscope
> > ./devtools/build-tags.sh tags x86_64-native-linuxapp-gcc
> > ./devtools/build-tags.sh gtags arm64-armv8a-linuxapp-gcc
> >
>
> This is great, Jerin, thank you!
>
> IMO it would be even better to have this as one of the targets in the master makefile rather than a standalone script, what do you think?
I had it in v2 and then I removed it.
If there are no objection, I will add these targets in Makefile in next
revision.
Example usage:
make tags T=x86_64-native-linuxapp-gcc
make tags
➜ [master]laptop [dpdk-master] $ git diff
diff --git a/mk/rte.sdkroot.mk b/mk/rte.sdkroot.mk
index 7598bde..cee53ff 100644
--- a/mk/rte.sdkroot.mk
+++ b/mk/rte.sdkroot.mk
@@ -92,6 +92,15 @@ default: all
config showconfigs showversion showversionum:
$(Q)$(MAKE) -f $(RTE_SDK)/mk/rte.sdkconfig.mk $@
+.PHONY: cscope gtags tags etags
+cscope gtags tags etags:
+ifdef T
+ $(Q)$(RTE_SDK)/devtools/build-tags.sh $@ ${T}
+else
+ $(Q)$(RTE_SDK)/devtools/build-tags.sh $@
+endif
+
+
>
next prev parent reply other threads:[~2017-03-21 4:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-27 0:12 [dpdk-dev] [PATCH] tools: " Jerin Jacob
2016-11-28 5:50 ` Yuanhan Liu
2017-01-12 14:19 ` Ferruh Yigit
2017-01-13 2:50 ` Jerin Jacob
2017-01-13 12:23 ` Mcnamara, John
2017-01-17 8:41 ` [dpdk-dev] [PATCH v2] " Jerin Jacob
2017-02-27 14:18 ` Thomas Monjalon
2017-02-28 14:12 ` Jerin Jacob
2017-03-01 10:51 ` Thomas Monjalon
2017-03-13 14:18 ` [dpdk-dev] [PATCH v3] devtools: " Jerin Jacob
2017-03-19 10:52 ` [dpdk-dev] [PATCH v4] " Jerin Jacob
2017-03-20 10:15 ` Dumitrescu, Cristian
2017-03-21 4:05 ` Jerin Jacob [this message]
2017-03-22 8:30 ` [dpdk-dev] [PATCH v5] " Jerin Jacob
2017-04-14 12:44 ` Jerin Jacob
2017-04-28 8:50 ` Thomas Monjalon
2017-04-29 10:51 ` [dpdk-dev] [PATCH v6] " Jerin Jacob
2017-04-30 10:45 ` Thomas Monjalon
2017-04-30 11:00 ` 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=20170321040521.n7cemveimnkxs5fz@localhost.localdomain \
--to=jerin.jacob@caviumnetworks.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).