CodeLite IDE

HI there

Thanks Eranif for getting back to me on sourceforge.
( here's the sourceforge link )
=> http://sourceforge.net/tracker/?func=de ... tid=979960

1) Clang issues.
"...If you got clang to fail on your code completion, it means that it could
not compile your sources. This brings me to my next question:
Do you use a custom makefile for building your sources, or are you using
codelite's build system?..."

We're using a custom makefile solution.
I guessed that clang was failing to compile our source. But the problem was that CodeLite gave us no feedback as to where it was failing to compile.
All I got was some strange error along the lines of "found '}' was expecting bool" or something.
No filename. No line number. Nothing. And on our very large codebase that was impossible to fix.
And it only came up when I tried do code completion. Maybe it should show the errors sooner than that. ( ie, in a log somewhere )
So at least give a filename and line number along with the error ( if possible ). That would go a long way to fixing clang-related problems.

2)
"...About your complain: " CodeCompletion and GoToDefinition features were not
working across namespaces correctly" - have you tried enabling the flag:
settings -> tags settings -> general -> scan all included files to locate
'using namespace' statements" ... "

Yes I did try this feature. ( I think ).
I remember trying almost everything.

Here's a more complete description of the namespace problem.
=> http://sourceforge.net/tracker/?func=de ... tid=979960

3)
I think it would be of benefit to have a "windows" menu in the menu bar. Similar to visual studio.
Have it show the most recently visited ( and still open ) files. ( and a star beside changed, yet unsaved, files )
This would make visual studio migration very much easier.

Thanks a lot for getting back to me.
And for all your hard work on codelite!
Brian

BrianSharpe wrote:We're using a custom makefile solution.
I guessed that clang was failing to compile our source. But the problem was that CodeLite gave us no feedback as to where it was failing to compile.
All I got was some strange error along the lines of "found '}' was expecting bool" or something

I am working on a solution for custom makefiles (there is already one, but I found it insufficient atm).
The idea is to record the build output and use the compilation flags per file later these flags can be passed to clang for compilation.

BrianSharpe wrote:"...About your complain: " CodeCompletion and GoToDefinition features were not
working across namespaces correctly" - have you tried enabling the flag:
settings -> tags settings -> general -> scan all included files to locate
'using namespace' statements" ... "

Yes I did try this feature. ( I think ).
I remember trying almost everything.

Well, fixing the first point will fix this one as well.
But I would like to fix it for ctags as well, as most people (including myself) are using ctags' code completion (well, its not really "ctags" but more of a built-in parser with ctags assistant

BrianSharpe wrote:I think it would be of benefit to have a "windows" menu in the menu bar. Similar to visual studio.
Have it show the most recently visited ( and still open ) files. ( and a star beside changed, yet unsaved, files )
This would make visual studio migration very much easier.

This one is doable, with small effort.

Also, have you tried using Ctrl-TAB?

Eran

FWIW, codelite 4.1 is out and should be able to code complete your workspace using clang now.
You will need to enable it and then perform a full rebuild (just once)

Eran

Hi Eran

Thanks for the code update.
I have tried codelite out on a small project now. And can confirm that the code navigation features now work across namespaces.
This is great. Thanks.

I am very busy at work, so am yet to set codelite up again with our larger project. But will get back to you when I do.

Thanks again
Brian