From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>, dev@dpdk.org
Cc: thomas.monjalon@6wind.com
Subject: Re: [dpdk-dev] [PATCH] tools: add tags and cscope index file generation support
Date: Thu, 12 Jan 2017 14:19:44 +0000 [thread overview]
Message-ID: <204efa1f-0631-ed9c-3d68-8c573edfbb76@intel.com> (raw)
In-Reply-To: <1480205562-32745-1-git-send-email-jerin.jacob@caviumnetworks.com>
On 11/27/2016 12:12 AM, Jerin Jacob wrote:
> This script generates cscope, gtags, and tags
> index files based on EAL environment.
> (architecture and OS(linux/bsd))
>
> Selection of the architecture and OS environment
> is based on dpdk configuration target(T=)
>
> example usage:
> make tags T=x86_64-native-linuxapp-gcc
> make cscope T=x86_64-native-linuxapp-gcc
> make gtags T=x86_64-native-linuxapp-gcc
>
> Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
<...>
> +
> +if [ -n "$T" ]; then
<...>
> + usage $1
> + exit
I would prefer fallback to RTE_TARGET parsing, or processing all files (
cscope -Rqn ), instead of exiting here, but that is your call.
Also "tags.sh" needs to be moved into "devtools" after latest updates.
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2017-01-12 14:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-27 0:12 Jerin Jacob
2016-11-28 5:50 ` Yuanhan Liu
2017-01-12 14:19 ` Ferruh Yigit [this message]
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
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=204efa1f-0631-ed9c-3d68-8c573edfbb76@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.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).