From: Marcelo Diop-Gonzalez <marcgonzalez@google.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH] trace-cmd: generate cscope.files when building cscope index
Date: Sun, 12 Jan 2020 14:05:37 -0500 [thread overview]
Message-ID: <20200112190537.170197-1-marcgonzalez@google.com> (raw)
Currently, running 'make cscope' gives this output:
rm -f cscope*
find . -name '\.pc' -prune -o -name '*\.[ch]' -print -o -name '*\.[ch]pp' ! -name '\.#' -print | cscope -b -q
cscope: no source files found
make: *** [Makefile:351: cscope] Error 1
By default, cscope looks in cscope.files for the list of
sources, so printing the source file list to this file
fixes the above error.
Signed-off-by: Marcelo Diop-Gonzalez <marcgonzalez@google.com>
---
Makefile | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index efd9ed4..0b15bf5 100644
--- a/Makefile
+++ b/Makefile
@@ -348,7 +348,8 @@ TAGS: force
cscope: force
$(RM) cscope*
- $(call find_tag_files) | cscope -b -q
+ $(call find_tag_files) > cscope.files
+ cscope -b -q
install_plugins_traceevent: force
$(Q)$(MAKE) -C $(src)/lib/traceevent/plugins install_plugins
--
2.20.1
next reply other threads:[~2020-01-12 19:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-12 19:05 Marcelo Diop-Gonzalez [this message]
2020-01-20 22:33 ` [PATCH] trace-cmd: generate cscope.files when building cscope index Steven Rostedt
2020-01-22 17:21 ` Marcelo Diop-Gonzalez
2020-01-22 17:28 ` Steven Rostedt
2020-01-22 18:49 ` Marcelo Diop-Gonzalez
2020-01-22 19:08 ` Steven Rostedt
2020-01-23 19:51 ` Marcelo Diop-Gonzalez
2020-01-23 21:08 ` Steven Rostedt
2020-01-23 21:11 ` Marcelo Diop-Gonzalez
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=20200112190537.170197-1-marcgonzalez@google.com \
--to=marcgonzalez@google.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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).