From: Nick Roberts <nickrob@snap.net.nz>
To: Kris Warkentin <kewarken@qnx.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Get make TAGS to work in gdb directory
Date: Wed, 28 Sep 2005 03:23:00 -0000 [thread overview]
Message-ID: <17210.3343.945649.693494@kahikatea.snap.net.nz> (raw)
In-Reply-To: <43317105.9040201@qnx.com>
Kris Warkentin writes:
> Wow! I had no idea that even existed. I always just did ctags `find .
> -name "*.[ch]"`. I suppose that the make TAGS is smart enough to only
> generate tags for the source files that have been configured for your
> target? How handy!
Actually, it creates TAGS for files that aren't compiled through ALLDEPFILES.
However it finds the tags for the source files that have been configured
first:
# Put the proper machine-specific files first, so M-. on a machine
# specific routine gets the one for the correct machine. (FIXME: those
# files go in twice; we should be removing them from the main list).
So in my case I find child_wait in linux-nat.c (compiled as part of my gdb)
and then inftarg.c (not compiled).
That comment and this one:
# Header files that need to have srcdir added. Note that in the cases
# where we use a macro like $(gdbcmd_h), things are carefully arranged
# so that each .h file is listed exactly once (M-x tags-search works
# wrong if TAGS has files twice). Because this is tricky to get
# right, it is probably easiest just to list .h files here directly.
seem inaccurate in that etags seems to ignore duplicate file names.
It might make sense just to include files that are configured in that if users
want them all they can just use ctags/etags directly as you have done. In any
case there seem to be other files in COMMON_OBS for which TAGS should be
generated e.g. annotate.c.
How about the patch below?
Nick
*** Makefile.in.~1.755~ 2005-09-28 15:08:01.000000000 +1200
--- Makefile.in 2005-09-28 15:10:07.388706664 +1200
***************
*** 886,897 ****
SOURCES = $(SFILES) $(ALLDEPFILES) $(YYFILES) $(CONFIG_SRCS)
# Don't include YYFILES (*.c) because we already include *.y in SFILES,
# and it's more useful to see it in the .y file.
! TAGFILES_NO_SRCDIR = $(SFILES) $(HFILES_NO_SRCDIR) $(ALLDEPFILES) \
$(CONFIG_SRCS)
TAGFILES_WITH_SRCDIR = $(HFILES_WITH_SRCDIR)
! COMMON_OBS = $(DEPFILES) $(CONFIG_OBS) $(YYOBJ) \
! version.o \
annotate.o \
auxv.o \
bfd-target.o \
--- 886,898 ----
SOURCES = $(SFILES) $(ALLDEPFILES) $(YYFILES) $(CONFIG_SRCS)
# Don't include YYFILES (*.c) because we already include *.y in SFILES,
# and it's more useful to see it in the .y file.
! TAGFILES_NO_SRCDIR = $(SFILES) $(HFILES_NO_SRCDIR) $(OTHER_COMMON_OBS) \
$(CONFIG_SRCS)
TAGFILES_WITH_SRCDIR = $(HFILES_WITH_SRCDIR)
! COMMON_OBS = $(DEPFILES) $(CONFIG_OBS) $(YYOBJ) $(OTHER_COMMON_OBS)
!
! OTHER_COMMON_OBS = version.o \
annotate.o \
auxv.o \
bfd-target.o \
next prev parent reply other threads:[~2005-09-28 3:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 22:27 Nick Roberts
2005-09-21 14:36 ` Kris Warkentin
2005-09-28 3:23 ` Nick Roberts [this message]
2005-09-26 1:39 ` Daniel Jacobowitz
2005-09-26 4:43 ` Nick Roberts
2005-09-26 13:25 ` Daniel Jacobowitz
2005-09-28 3:01 ` Nick Roberts
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=17210.3343.945649.693494@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=gdb-patches@sources.redhat.com \
--cc=kewarken@qnx.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