path: root/scripts
diff options
authorDaniel Vetter <daniel.vetter@ffwll.ch>2009-11-26 13:34:12 +0100
committerMichal Marek <mmarek@suse.cz>2009-12-12 13:08:16 +0100
commiteb8f844c0a41c4529a7d06b7801296eca9ae67aa (patch)
tree51609ceb291a7f2bceae4ee605dc90ad8088aa7c /scripts
parent32197c7ffb06b1319850f8fdfa1a49d32a63b79b (diff)
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>
Diffstat (limited to 'scripts')
1 files changed, 7 insertions, 1 deletions
diff --git a/scripts/tags.sh b/scripts/tags.sh
index d52f7a01557c..1a0c44d7c4a7 100755
--- a/scripts/tags.sh
+++ b/scripts/tags.sh
@@ -89,7 +89,13 @@ all_defconfigs()
- (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

Privacy Policy