Performance problems in CMake support

[Aleix]

By finder I mean a Find<PackageName>.cmake. A lot of regular expressions is
used there.

The problem is that I am reparsing the project every time (looking for all
the executables and so) and now I should implement some CMakeCache.txt. I
hope that this will bring some speed to the project construction. I've
thought about being able to open only a part of the project too, this would
make it a little bit faster as well, you should take in account that a kde
module is a big project itself...

It would be is to save the state of the project when closing so that when we
open it another time it opens faster, but btw, the way cmake has to go is to
be builddir dependent (as I said about the cmakecache.txt use).

Bye,
Aleix

On Tue, Apr 1, 2008 at 2:03 AM, Andreas Pakulat <apaku at gmx.de> wrote:

> On 01.04.08 00:39:42, Aleix wrote:
> > Hi andreas,
> > Yes, I've ran callgrind too and it seems that this qregexp is spent by
> > the finders so there is no much to do on the code.
>
> finders? Could you elaborate a bit? I haven't yet looked at the cmake
> code enough to understand that term.
>
> Andreas
>
> --
> Tuesday After Lunch is the cosmic time of the week.
>
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20080401/8eb706bd/attachment.html>