I cannot get CScope to work. When searching for functions that call or are called from a function, cscope reports "+cannot". Expanding "+cannot" provides a list of files. It looks like all the files in my project. Each line says "Line: 0, open, <file path>. If I open a DOS box and type "cscope" I get "error opening terminal: cygwin". Then it creates a cscope.xxxx directory that is empty where the xxxx are random numbers. I have only one copy of cygwin1.dll and it is in my Program Files\CodeLite directory. I tried copying it to \Windows\System32, but no joy. Any ideas?
EDIT
Well good news! It is working now. I believe it began working after I cleaned up some obsolete entries in my codelite.xml and session.xml files and removed the link to a corrupt project file (not the active project) in my *.workspace file.
Last edited by KEhrhardt on Wed Jan 28, 2009 9:23 pm, edited 1 time in total.
From above -> If I open a DOS box and type "cscope" I get "error opening terminal: cygwin". Note that the workspace, project and code exist on a network drive, not my local hard disk if that matters at all. I thought that perhaps CodeLite could not find the cygwin1.dll, so I copied it from the CodeLite directory (my only copy) to \Windows\system32, since it is the first directory on my path. Cscope does work now, although it is quite slow finding the calling/called functions.
When searching for functions that call or are called from a function, cscope reports "+cannot". Expanding "+cannot" provides a list of files. It looks like all the files in my project. Each line says "Line: 0, open, <file path>. If I open a DOS box and type "cscope" I get "error opening terminal: cygwin". Then it creates a cscope.xxxx directory that is empty where the xxxx are random numbers. I have only one copy of cygwin1.dll and it is in my Program Files\CodeLite directory. I tried copying it to \Windows\System32, but no joy. 
Any ideas?
But cscope is working, so I am happy. 