Code::Blocks Forums
User forums => Using Code::Blocks => Topic started by: raynebc on April 29, 2016, 10:27:23 pm
-
I'd never used this plugin before, but I find that if I try to use the "Find functions called by" or "Find functions calling" functions, the Cscope log tab is displayed as empty and "error while calling cscope occurred" is displayed in the status area at the bottom of the log pane. Is there something I'm missing here? Running the 4-11-2016 nightly build of C::B on Windows 7 Pro x64.
-
You have to install cscope executable (see: http://wiki.codeblocks.org/index.php/Cscope_plugin ).
The plugin just calls it.
-
Thank you. Unfortunately the cscope project doesn't offer binaries and their code won't build with MinGW/MSYS (needs sys/wait.h which I guess doesn't exist in MinGW). I was able to find a build on the Internet though (https://easy-vim.googlecode.com/files/cscope.exe) and it seems to work fine.
-
Excuse me for reopening, I'm having the same problem. I downloaded the executable cscope.exe but how can I "install" it? I found a "Cscope" folder in my \shared\codeblocks path, but it's zipped and contains only a manifest file.
Thanks N. Cassetta
-
I placed it in my compiler's bin directory, but as long as you put it in one of the folders in your PATH environment variable (so that you can call it from the command line at any working directory) you should be good to go.
-
Ok, thanks!
-
I found a "Cscope" folder in my \shared\codeblocks path, but it's zipped and contains only a manifest file.
That's part of the cscope-plugin.
-
Having cscope.exe in directory present in %PATH% is not enough. I'm using C::B 17.12 and cscope started to work after putting it to C:\Program Files (x86)\CodeBlocks\MinGW\bin
Correction:
It is not true. Having cscope in directory present in %PATH% is enough. My fault was caused by having different PATH in system and in Command Prompt.
Adam
-
With a never version (current nightly) there is a new option to set the path to the cscope executable in Settings->Environment->CScope