Initial Impressions 1.0 (continued)
Posted: Wed Sep 23, 2009 4:05 am
Don't get me wrong -- I like CodeLite -- these are just issues that chafe. 
[11] The stripping of the prefix 'lib' and postfix '.a' from library names can create confusion. The fact that gcc and g++ does it, requires no extra help from the IDE. There is an attempt at being helpful by introducing semi-colons as pseudo command line delimiters. But it isn't done consistently. Some dialog boxes delimit by space some by newline and some by semi-colon and some by check-box.
[12] The check-box list of gcc flags is far from complete. If I have to enter any flags 'manually', that is on a space delimited command line, I might as well do them all.
[13] A single check for -pg to turn on profiling for both compiling and linking (and to force a clean build) would be useful.
[14] CodeLite picks up on *.lib files and tries to feed them to gcc. Each compiler should have a nameable set of file types that it is allowed to deal with. Given freetype6.a and freetype6.lib only the former should be fed to gcc.
[15] I found starting CodeLite with a pre-existing set of code rather peculiar. The intial main.c with Hello World stuff had to be disposed of which I found disconcerting.
[16] Better documentation on what are called 'virtual folders' in a project but are perhaps better described as 'automatically found, plausible dependencies' in the project would help.
Excuse, what is possibly at times a rant
-- I have been using CodeLite every day for only the past two weeks.
[11] The stripping of the prefix 'lib' and postfix '.a' from library names can create confusion. The fact that gcc and g++ does it, requires no extra help from the IDE. There is an attempt at being helpful by introducing semi-colons as pseudo command line delimiters. But it isn't done consistently. Some dialog boxes delimit by space some by newline and some by semi-colon and some by check-box.
[12] The check-box list of gcc flags is far from complete. If I have to enter any flags 'manually', that is on a space delimited command line, I might as well do them all.
[13] A single check for -pg to turn on profiling for both compiling and linking (and to force a clean build) would be useful.
[14] CodeLite picks up on *.lib files and tries to feed them to gcc. Each compiler should have a nameable set of file types that it is allowed to deal with. Given freetype6.a and freetype6.lib only the former should be fed to gcc.
[15] I found starting CodeLite with a pre-existing set of code rather peculiar. The intial main.c with Hello World stuff had to be disposed of which I found disconcerting.
[16] Better documentation on what are called 'virtual folders' in a project but are perhaps better described as 'automatically found, plausible dependencies' in the project would help.
Excuse, what is possibly at times a rant
-- I have been using CodeLite every day for only the past two weeks.