On Mon, Nov 30, 2009 at 07:11:09PM +0100, Sam Ravnborg wrote: > 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. I've just tried to use cscope with a working directory not equal to the directory where cscope.out resides: $ cscope -d -f src/cscope.out It can't handle relative paths. When I try to open a file (via a reference) from within cscope, it calls up vim with the wrong path. So I think this is a fundamental cscope bug (and not a vim problem). As I've already said, every tutorial on the web I could find uses absolute paths, too, so the problem seems to be common, as is the work-around. Therefore please apply this patch (perhaps changing my comment to "cscope is broken with relative paths, work around it via absolute paths"). Thanks, Daniel -- Daniel Vetter Mail: daniel@xxxxxxxx Mobile: +41 (0)79 365 57 48 -- 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
