Re: [PATCH v2 1/2] scripts/tags.sh: Resolve gtags empty index generation

Ahmed S. Darwish
2023-05-15T15:23:59Z

On Fri, 12 May 2023, Masahiro Yamada wrote:
>
> The code works as claimed, but I am just curious.

Thanks.

> If all the paths are relative, how can you use the tags files located
> in a separate directory?
>
> "make O=foo gtags" creates tags files in foo/.
> I want to use them from emacs.
> emacs cannot find the right file because
> it assumes the path is relative to 'foo' instead of the source tree.
>

Correct.

In theory, since all the indexed linux source tree paths at the gtags
generated files (GPATH/GRTAGS/GTAGS) are relative to the linux source
tree root, opening such files from emacs ggtags-mode, *wherever* these
files are, "should" work.

In practice, ggtags/global (and thus also emacs ggtags-mode) operate
with a model of the world where all indexed files must be under the
source "root directory". So, the GPATH/GRTAGS/GTAGS files are expected
to be under the source tree (except in special GTAGSLIBPATH= cases).

> I set GTAGSROOT to the source tree, but I could not find a way
> to use it in a useful way.

Yes, that won't work, as emacs will search for the G* database files
under that folder instead.

Meanwhile setting GTAGSROOT to the O= directory, or to a build directory
that is different from the kernel source tree, as in:

cd ~/linux
O=~/build/build-linux-x86
make O=$O x86_64_defconfig
make O=$O gtags
GTAGSROOT=$O emacs init/main.c

will "mostly" succeed (as you hinted at):

M-x ggtags-mode

# emacs finds gtags files under ${GTAGSROOT} and sets ${GTAGSROOT} as
# the root of the project

M-x ggtags-find-definition
Definition: rcu_read_lock

-*- mode: ggtags-global; default-directory: "~/build/build-linux-x86/" -*-
Global started at Mon May 15 15:54:01

global -v --result=grep --color=always --path-style=shorter -- rcu_read_lock
include/linux/rcupdate.h:769:static __always_inline void rcu_read_lock(void)
1 object located (using '/home/darwi/build/build-linux-x86/GTAGS').

Global found 1 definition at Mon May 15 15:54:01

# Prompt
Find this match in (default include/linux/rcupdate.h)?: ~/build/build-linux-x86/
^^^

But at the Prompt step above, things break.

In a fully working setup, this prompt will not be shown and emacs just
jumps to rcuupdate.h line 769.

What I personally do to mitigate that problem is:

cd ~/linux
for f in GTAGS GRTAGS GPATH; do
ln -vsf ${O}/$f .
done

and switch these symlinks through minor local shell plumbing whenever
I'm switching kernel projects with different build directories.

It is not ideal, but maybe we can discuss this with the global(1) people
at a later step. At least with this patch series, "make O=xyz/ gtags"
produces a valid index.

>
> > +# gtags(1) refuses to index any file outside of its current working dir.
> > +# If gtags indexing is requested and the build output directory is not
> > +# the kernel source tree, index all files in absolute-path form.
> > +if [ "$1" = "gtags" -a -n "${tree}" ]; then
> > + tree=$(realpath $tree)/
>
> I decided to run shellcheck for new code.
> Please follow the suggestion from the tool.
>
> In scripts/tags.sh line 40:
> tree=$(realpath $tree)/
> ^---^ SC2086 (info): Double quote to prevent
> globbing and word splitting.
>
> Did you mean:
> tree=$(realpath "$tree")/
>
> (You do not need to fix the entire script.
> This is only for new code).
>

Yes, the reason was to following the existing coding pattern at
scripts/tags.sh. But, sure, will do.

>
> > @@ -131,7 +139,11 @@ docscope()
> >
> > dogtags()
> > {
> > - all_target_sources | gtags -i -f -
> > + local gtagsoutdir="${PWD}"
> > + local gtagsroot="${tree}"
> > +
> > + [ -z "${gtagsroot}" ] && gtagsroot="."
> > + all_target_sources | gtags -i -C $gtagsroot -f - $gtagsoutdir
> > }
>
> You can write it in one line.
>
> dogtags()
> {
> all_target_sources | gtags -i -C "${tree:-.}" -f - "${PWD}"
> }
>

Ditto. The script was almost-fully POSIX style (except the first line),
so I avoided bash features on purpose.

I personlly always prefer using Bash features though, so I'll definitely
update the code.

Thanks a lot for the review. I'll send a v3.

--
Ahmed S. Darwish
Linutronix GmbH