From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: daniel@iogearbox.net, ast@fb.com
Cc: "Toke Høiland-Jørgensen" <toke@redhat.com>,
andriin@fb.com, bpf@vger.kernel.org, netdev@vger.kernel.org
Subject: [PATCH bpf-next] libbpf: Add cscope and TAGS targets to Makefile
Date: Thu, 3 Oct 2019 10:43:21 +0200 [thread overview]
Message-ID: <20191003084321.1431906-1-toke@redhat.com> (raw)
Using cscope and/or TAGS files for navigating the source code is useful.
Add simple targets to the Makefile to generate the index files for both
tools.
Signed-off-by: Toke Høiland-Jørgensen <toke@redhat.com>
---
tools/lib/bpf/.gitignore | 2 ++
tools/lib/bpf/Makefile | 10 +++++++++-
2 files changed, 11 insertions(+), 1 deletion(-)
diff --git a/tools/lib/bpf/.gitignore b/tools/lib/bpf/.gitignore
index d9e9dec04605..c1057c01223e 100644
--- a/tools/lib/bpf/.gitignore
+++ b/tools/lib/bpf/.gitignore
@@ -3,3 +3,5 @@ libbpf.pc
FEATURE-DUMP.libbpf
test_libbpf
libbpf.so.*
+TAGS
+cscope.*
diff --git a/tools/lib/bpf/Makefile b/tools/lib/bpf/Makefile
index c6f94cffe06e..57df6b933196 100644
--- a/tools/lib/bpf/Makefile
+++ b/tools/lib/bpf/Makefile
@@ -262,7 +262,7 @@ clean:
-PHONY += force elfdep bpfdep
+PHONY += force elfdep bpfdep cscope TAGS
force:
elfdep:
@@ -271,6 +271,14 @@ elfdep:
bpfdep:
@if [ "$(feature-bpf)" != "1" ]; then echo "BPF API too old"; exit 1 ; fi
+cscope:
+ (echo \-k; echo \-q; for f in *.c *.h; do echo $$f; done) > cscope.files
+ cscope -b -f cscope.out
+
+TAGS:
+ rm -f TAGS
+ echo *.c *.h | xargs etags -a
+
# Declare the contents of the .PHONY variable as phony. We keep that
# information in a variable so we can use it in if_changed and friends.
.PHONY: $(PHONY)
--
2.23.0
next reply other threads:[~2019-10-03 8:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 8:43 Toke Høiland-Jørgensen [this message]
2019-10-03 17:14 ` [PATCH bpf-next] libbpf: Add cscope and TAGS targets to Makefile Andrii Nakryiko
2019-10-04 9:27 ` Toke Høiland-Jørgensen
2019-10-04 14:36 ` Andrii Nakryiko
2019-10-04 14:39 ` Andrii Nakryiko
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=20191003084321.1431906-1-toke@redhat.com \
--to=toke@redhat.com \
--cc=andriin@fb.com \
--cc=ast@fb.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.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).