Commit eb8f844c authored Nov 26, 2009 by Daniel Vetter Committed by Michal Marek Dec 12, 2009

kbuild: specify absolute paths for cscope



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>

parent 32197c7f

scripts/tags.sh

+7 −1

Original line number	Diff line number	Diff line
		@@ -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
		}

Admin message