Some tools (like my favourite editor, vim) can't handle relative
paths from cscope as soon as cscope.out is no longer 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).
Signed-off-by: Daniel Vetter <daniel.vetter@xxxxxxxx>
---
scripts/tags.sh | 4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/scripts/tags.sh b/scripts/tags.sh
index d52f7a0..49bffed 100755
--- a/scripts/tags.sh
+++ b/scripts/tags.sh
@@ -89,7 +89,9 @@ all_defconfigs()
docscope()
{
- (echo \-k; echo \-q; all_sources) > cscope.files
+ # use absolute paths - vim likes it that way
+ tree=$PWD/$tree
+ (cd /; echo \-k; echo \-q; all_sources) > cscope.files
cscope -b -f cscope.out
}
--
1.6.5.3
--
To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
