Profiling CMake Support

[Andreas Pakulat]

Hi,

just finished what I've discussed with Aleix a while back: A
stripped-down unit-test that executes the same code as CMakeManager
class for parsing a project. Its in
projectmanagers/cmake/tests/cmakeloadprojecttest and has 3 test
functions for:

- a plain cmake project in tests/manual/tiny_project
- a Qt4 Only cmake project in tests/manual/qt4app
- a KDE4 cmake project in tests/manual/kde4app

When running the test you can choose one of the test functions to
execute and can even let QTest generate the callgrind output by doing

./cmakeloadprojecttest -callgrind testSmallQt4Project

Not sure what/where the output lands (still running here), but this
should give us an easy way of profiling the actual parsing+duchain
building without the overhead of creating items from the results. It
already shows that there's not a huge difference between Qt4 and KDE4
projects. However the plain cmake project is a lot faster (well its also
smaller, still just the FindQt4 shouldn't produce such a big overhead).

Andreas

-- 
Chicken Little only has to be right once.