On Mon, Nov 30, 2009 at 06:13:47PM +0100, Michal Marek wrote: > On 26.11.2009 13:34, Daniel Vetter wrote: > > 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). > > But it will fail if you rename the source directory. I'm not sure what > is worse, I myself don't use cscope much. Fixing vim would be the ideal > solution of course (it already handles ../tags fine). For tags I recall we fall back to absolute path only for O=... builds. This made the tags file considerably smaller for a non O=.. build thus speeding up the search. So unconditionally using absolute paths for cscope may have drawbacks. Sam -- 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
