Ben Fritz wrote:
> From the cmd.exe prompt, I can successfully navigate the code using:
> cscope.exe -f C:/Temp/projname.cscope.out -i C:/Temp/
> projname.cscope.files
>
> But when I then try to use it within Vim with the following command:
> cscope add C:/Temp/projname.cscope.out -i C:/Temp/
> projname.cscope.files
>
> I get:
> E563: stat(C:/Temp/projname.cscope.out) error: 2

It looks like a severe problem so I will blurt out some thoughts
despite not having used Cscope for a few years (and not really
having a clue).

I think the '2' is error ENOENT
    No such file or directory.
    A component of a specified pathname did not exist,
    or the pathname was an empty string.

so I guess that cscope (or Vim?) thinks that file
C:/Temp/projname.cscope.out does not exist.

I wonder what cscope does with a path like C:/Temp/whatever
(will the forward slashes work?).

You might fiddle with setting verbose levels in Vim to see if
more info is displayed.

You say you can navigate the code using cscope.exe, so I assume
you have used -b to build the database. I wonder what directory
that database is in. I would be inclined to make a new directory
and put a few test source files in it, then try all your
commands while working in that directory (so there is no need
for a path to anything). I would make sure the directory path is
short with no spaces just for safety, and I would copy
cscope.exe and sort.exe into that directory so there is no risk
of any dodgy files coming first in the PATH.

My old notes include a cryptic message that I obtained file
env.exe from unxtools and put it early in my PATH. It sets the
environment for a spawned program and is used by the 2004
version of Cscope I last used (to call sort.exe?). By the way,
unxtools is obsolete; if I were looking now I would go to
http://gnuwin32.sourceforge.net/

John


--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to