This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Patch: `make tags' -vs- gdbtk, try 2


I first submitted this patch on November 21.  This resubmission
refines the patch to correctly find the gdbtk `.h' files and to
correctly make tags for gdbtk hooks.  If gdbtk isn't checked out, it
should have no effect.

Is this ok to commit?

In general how long should I wait before pinging about a patch?  In
this case I figured 10 days was long enough for a relatively simple
Makefile patch.

2000-12-02  Tom Tromey  <tromey@redhat.com>

	* Makefile.in (TAGS): Correctly find gdbtk .c/.h files.  Also,
	generate tags for gdbtk Tcl sources.

Tom

Index: Makefile.in
===================================================================
RCS file: /cvs/src/src/gdb/Makefile.in,v
retrieving revision 1.47
diff -u -r1.47 Makefile.in
--- Makefile.in	2000/11/10 23:02:56	1.47
+++ Makefile.in	2000/12/02 18:58:11
@@ -871,11 +871,18 @@
 	  $(srcdir)/$(XM_FILE) \
 	  $(srcdir)/$(NAT_FILE) \
 	`(for i in $(DEPFILES) $(TAGFILES_NO_SRCDIR); do \
-		echo $(srcdir)/$$i ; \
+		case "$$i" in \
+		  gdbtk*) ;; \
+		  *) echo $(srcdir)/$$i ;; \
+		esac; \
 	done ; for i in $(TAGFILES_WITH_SRCDIR); do \
 		echo $$i ; \
 	done) | sed -e 's/\.o$$/\.c/'` \
-	`find $(srcdir)/config -name '*.h' -print`
+	`find $(srcdir)/config -name '*.h' -print` \
+	`find $(srcdir)/gdbtk -name '*.[ch]' -print` \
+	--lang=none \
+	--regex='/[ \t]*\(proc\|method\|itcl_class\|body\|define_hook\)[ \t]+\([^ \t]+\)/\1/' \
+	`find $(srcdir)/gdbtk \( -name '*.tcl' -o -name '*.ith' -o -name '*.itb' \) -print`
 
 tags: TAGS
 

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]