Skip to content

Commit

Permalink
kbuild: specify absolute paths for cscope
Browse files Browse the repository at this point in the history
Cscope doesn't hadle relative paths when cscope.out is not in $PWD. Use
absolute paths when generating cscope.files, which seems to be the
recommended way to generate cscope.out, anyway (at least according to
cscope.sf.net). The speed and size differences are minimal, the only
drawback is that the database needs to be regenerated if the source
directory is moved.

[mmarek: fixed for O= builds, modified changelog]

Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Michal Marek <mmarek@suse.cz>
  • Loading branch information
Daniel Vetter authored and Michal Marek committed Dec 12, 2009
1 parent 32197c7 commit eb8f844
Showing 1 changed file with 7 additions and 1 deletion.
8 changes: 7 additions & 1 deletion scripts/tags.sh
Original file line number Diff line number Diff line change
@@ -89,7 +89,13 @@ all_defconfigs()

docscope()
{
(echo \-k; echo \-q; all_sources) > cscope.files
# always use absolute paths for cscope, as recommended by cscope
# upstream
case "$tree" in
/*) ;;
*) tree=$PWD/$tree ;;
esac
(cd /; echo \-k; echo \-q; all_sources) > cscope.files
cscope -b -f cscope.out
}

0 comments on commit eb8f844

Please sign in to comment.