On Wed, 14 Jul 2004, Jesse Barnes wrote:
It looks like this rule will include source files which are not incorporated by Makefile.am since it appears to simply recurse through the source tree. That means it may pick up source files from other projects, or source files which are not in use. Is that what you intended?
Kind of. It looks like gtags does that, so I followed its example. It might be better to only include those explicitly listed by Makefile.am, but I wasn't sure of the best way to get the full list of source files... OTOH, maybe it's best to index the whole project.
Probably gtags is not implemented very well.
It seems like there should be a rule to collect the source file list from all Makefiles (including subordinate Makefiles) followed-up by another rule which actually executes cscope using the file list.
If the build is a VPATH build, then the source directory tree should be treated as read-only, with the cscope database being built in the build directory. This allows multiple architectures to use cscope without trashing each other's databases (the cscope database format appears to be architecture dependent).
Indexing everything under the source tree doesn't make sense since the software may not be related, or there may replicated source files.
Bob ====================================== Bob Friesenhahn [EMAIL PROTECTED] http://www.simplesystems.org/users/bfriesen
