Re: [suggestion] new target GTAGS.

> ">" == Shigio Yamaguchi <[EMAIL PROTECTED]> writes: >> In BSD system, '/usr/obj' + is used for build >> directory. (from now on, I say it 'obj' directory.) >> If there is a convention in automake, I can support it. There isn't a simple convention like this. The person building the packa

Re: [suggestion] new target GTAGS.

> Here is what I'm adding: > > ## Support `Global' tags. > GTAGS: > here=`cd $(top_builddir) && pwd` && cd $(top_srcdir) && gtags -i $$ here All right. Thank you. > >> By the way, where does automake put tag files to? > > It puts them in the build directory. > This might be t

Re: [suggestion] new target GTAGS.

> ">" == Shigio Yamaguchi <[EMAIL PROTECTED]> writes: >> Yes, it does. The following command line makes tag files in >> /var/obj instead of current directory. >> % gtags /var/obj Thanks. >> But gtags must be invoked in the root of source directory. Here is what I'm adding: ## Su

Re: [suggestion] new target GTAGS.

> I'm not against doing this. Since GTAGS is a GNU program, and one of > automake's goals is to work well with other GNU programs, it seems > like a reasonable idea. I'm glad to hear that. > I'm curious: what advantage does global give over etags or idutils? Most important advantage is that G

Re: [suggestion] new target GTAGS.

> ">" == Shigio Yamaguchi <[EMAIL PROTECTED]> writes: >> How about adding new target 'GTAGS' that means GLOBAL's tag to >> automake? I'm not against doing this. Since GTAGS is a GNU program, and one of automake's goals is to work well with other GNU programs, it seems like a reasonable idea

[suggestion] new target GTAGS.

Hello, How about adding new target 'GTAGS' that means GLOBAL's tag to automake? GNU GLOBAL is a source code tag system that works the same way across diverse environments. It supports C, C++, Yacc and Java source code. [simple usage] % cd /usr/sr