Commit eb8f844c authored by Daniel Vetter's avatar Daniel Vetter Committed by Michal Marek

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 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: default avatarDaniel Vetter <>
Signed-off-by: default avatarMichal Marek <>
parent 32197c7f
......@@ -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 ;;
(cd /; echo \-k; echo \-q; all_sources) > cscope.files
cscope -b -f cscope.out
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment