How do you do it in Windows. How to tell windows cmd shell to change directory to the project folder and build cscope DB there?

+

:The directory change is easy, just use the "cd" command just like on Unix (but with backslash separators). The harder part is getting a list of files. You might be able to use <code>dir /b /s *.c</code> and the same for *.h, or you could use Vim to create the list of files using {{help|prefix=no|glob()}} or {{help|prefix=no|globpath()}}. Other than that, cscope itself works in pretty much the same way no matter what system you're on. --[[User:Fritzophrenic|Fritzophrenic]] ([[User talk:Fritzophrenic|talk]]) 15:46, July 2, 2013 (UTC)

+

::But, how to pass the current working directory information to "cd", and then how to run cscope from that directory ?

+

:::Just like for any other external command. Actually from within Vim, you can just use Vim's built-in {{help|prefix=no|:cd}} command to get to the directory you want. Or use {{help|prefix=no|:lcd}}. Then use <code>:!path\to\cscope.exe</code> to run cscope from that directory. If you must, you can use the cmd.exe cd command instead, like <code>:!cd some\path & path\to\cscope.exe</code>. If you need Vim's current directory, you can use {{help|prefix=no|getcwd()}}. --[[User:Fritzophrenic|Fritzophrenic]] ([[User talk:Fritzophrenic|talk]]) 19:54, July 3, 2013 (UTC)

In the above mapping, I use "find" to collect the C/C++ source code files and (re)create the cscope database; then "kill -1" to kill all cscope database connections and finally, the newly created "cscope.out" database is added by "cs add cscope.out".

There are two limitations in this key mapping:

the current directory should be the root path of the project

I don't know how to get the current cscope data connection number, so that I use "kill -1" to kill "all" cscope database connections, since actually I always only create one connections in one Vim instance. It is not practical if you are using multiple data connections in one Vim instance.

Related to limitation #2 above, it's not actually necessary to kill the cscope connection. The command cs reset can accomplish this purpose, if cscope.out is already selected as the cscope file. This gives the following variant:

How do you do it in Windows. How to tell windows cmd shell to change directory to the project folder and build cscope DB there?

The directory change is easy, just use the "cd" command just like on Unix (but with backslash separators). The harder part is getting a list of files. You might be able to use dir /b /s *.c and the same for *.h, or you could use Vim to create the list of files using glob() or globpath(). Other than that, cscope itself works in pretty much the same way no matter what system you're on. --Fritzophrenic (talk) 15:46, July 2, 2013 (UTC)

But, how to pass the current working directory information to "cd", and then how to run cscope from that directory ?

Just like for any other external command. Actually from within Vim, you can just use Vim's built-in :cd command to get to the directory you want. Or use :lcd. Then use :!path\to\cscope.exe to run cscope from that directory. If you must, you can use the cmd.exe cd command instead, like :!cd some\path & path\to\cscope.exe. If you need Vim's current directory, you can use getcwd(). --Fritzophrenic (talk) 19:54, July 3, 2013 (UTC)