codelite is an open-source, cross platform IDE for the C/C++ programming languages (build and tested on Windows 7, Ubuntu 12.04 / 12.10, and Mac OSX 10.8.4). codelite is distributed under the terms of the GPLv2 license
If you need help with codelite, please join our forums at:
Visit our download page at:
The CodeLite Team
Non-intuitive IDE. First, I installed CodeLite. Then, I made a new file, main.c, and wrote a simple hello world. But the build options are not highlighted, and there is no indication of why. I search it, turns out you need to create a workspace (and one isn't created when you first start CodeLite or install it). OK, fine. I make a new workspace called "workspace". Now I can make a new project in the workspace. Hey, a default hello world template was created in the project! Nice, I compile, and.... no errors. Great! I run, and... no executable found. I look at the compile messages, and it says "The directory is invalid." "No errors found. 0 errors, 0 warnings." No idea how the directory is invalid if I used the default workspace and their project creation wizard that automatically picks the directory. I'm not going to look into it further, I'm going to find a different IDE.
I think this program is great and simple to use. Finally Visual Studio IDE clone on Linux. Except there were show-stoppers for me. 1) CodeCompletion and GoToDefinition features were not working across namespaces correctly. This completely killed these must have features. Until this is fixed I cannot use codelite. :( It has to be Eclipse 2) No "Windows" menu on the menu bar. Small deal but it is much faster/easier to navigate through your last ~10 opened files, that the tab groups thing. This is what visual studio users are used to. To really succeed at drawing visual studio lovers it needs this. 3) General flakeyness with its code tagging. Clang had trouble parsing our codebase. And the only error I could get out of codelite was a simple " Expected 'bool', got '}' " style compiler error which gave no filename or linenumber. Impossible to do anything with on an extremely large codebase. And that was only when I went to do some code completion stuff. We need decent error reporting from the tagging so we can see where its breaking. ( on both clang and ctags ) Until these 3 things are fixed, I'll be going back to Eclipse. Although its interface is not as clean or simple, its generally more robust at handling+parsing large Makefile-based codebases. ( most unix systems are makefile based ) Brian
pretty good but code::blocks might have an edge imo. couldnt get console program to run after compiling in c++ a simple hello world program. even though it ran with the ide it didnt run alone after double clicking.