Commit e93bc1a0 authored Mar 08, 2010 by Michal Marek

Revert "kbuild: specify absolute paths for cscope"



This reverts commit eb8f844c. Ian
Campbell writes:
> I keep my kernel source tree on a more powerful build box where I run my
> builds etc (including "make cscope") but run my editor from my
> workstation with an NFS mount to the source. This worked fine for me
> using relative paths for cscope. Using absolute paths in cscope breaks
> this previously working setup because the root path is not the same on
> both systems. I guess this is similar to moving the source tree around.
>
> Without wanting to start a flamewar it really sounds to me like we are
> working around a vim (or cscope) bug here, emacs with cscope bindings
> works fine in this configuration.

Given that absolute paths can be forced by make O=. cscope, change the
default back to relative paths.

Ian Campbell <ijc@hellion.org.uk>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Michal Marek <mmarek@suse.cz>

parent a6c36632

scripts/tags.sh

+3 −7

Original line number	Diff line number	Diff line
		@@ -18,6 +18,8 @@ ignore="( -name SCCS -o -name BitKeeper -o -name .svn -o \
		-prune -o"

		# Do not use full path if we do not use O=.. builds
		# Use make O=. {tags\|cscope}
		# to force full paths for a non-O= build
		if [ "${KBUILD_SRC}" = "" ]; then
		tree=
		else
		@@ -108,13 +110,7 @@ all_defconfigs()

		docscope()
		{
		# 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
		(echo \-k; echo \-q; all_sources) > cscope.files
		cscope -b -f cscope.out
		}

Admin message