Re: [PATCH] build: generate cscope and etags source indexes

[Tomi Ollila <tomi.ollila@iki.fi>]

On Thu, Aug 24 2017, Jani Nikula wrote:

> On Wed, 23 Aug 2017, Yuri Volchkov <yuri.volchkov@gmail.com> wrote:
>> Just a handy tool to generate source code indexes for your favorite
>> editor.
>>
>> To make tags for vim run:
>>   $ make cscope
>> To make tags for emacs:
>>   $ make TAGS
>> To make both:
>>   $ make alltags
>
> What's the point in adding these to configure? Or, to be honest, to the
> build at all?

I agree with Jani about configure and build steps, but could tolerate
convenience goals like `cscope` and `tags` (and something `global` !)
which would build corresponding files for developers to utilize (provided
those are accurate enough, we don't want to lessen general quality (from
what it is now) of the system due to too bad quality tags files
(content-wise)...

Tomi (who should get to work with gnu global again...)

>
> In theory you'll be able to look at $(SRCS) for indexing... but those
> are only the .c/.cc files. Are your tools clever enough to follow
> #include directives to index the headers as well?
>
> I guess I'm also biased because I use gnu global [1] instead. And for
> that I have a script of my own that basically boils down to:
>
> $ git ls-files | gtags -f -

(... which means I have to try git ls-files --recurse-submodules | gtags -f -)

>
> which means all files tracked by git get indexed, and global will decide
> whether it can index the file or not.
>
> BR,
> Jani.
>
> [1] https://www.gnu.org/software/global/
>
>>
>> Signed-off-by: Yuri Volchkov <yuri.volchkov@gmail.com>