On Thursday 1 June 2006 17:33, you wrote: > Thomas Zander zander at kde.org wrote: > >Correct me if I misunderstood; but AFAICS the current idea was to > > parse all config files (which in case of KOffice takes several > > minutes with clean caches) and present the options based on that. > >If you want to do that I suggest to not show in anyway that its cmake, > > as the user will hate cmake immediately ;) > > You misunderstood! There were two suggestions: the configuration file > and the parsing in "do nothing" mode which would > only analyse which OPTION variables are currently > enabled. The latter boils down to merely reading all the CMakeLists.txt > files of the project and the current CMakeCache.txt, > and I am rather sure your koffice project is not that > big that reading all the CMakeLists.txt files could not be done > even with an shell script in a few seconds only!
You'd be wrong there; time find . -name CMakeLists.txt [snip] real 0m49.669s user 0m0.144s sys 0m0.796s Naturally; that with clean caches; doing it a second time gives me an immediate result. But I _was_ talking about first impressions. This incidently is also a major pain in the * for me; if I do a gdb session it will take all my memory and I end up waiting an additional minute for a make to start. ps; a wc -l returns 502. -- Thomas Zander
pgpGPGGwqvmGw.pgp
Description: PGP signature
_______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
