[CMake] Re: a ./configure shell script stub Thoma Zander
Thomas Zander
zander at kde.org
Thu Jun 1 11:40:58 EDT 2006
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
Url : http://public.kitware.com/pipermail/cmake/attachments/20060601/256c79b6/attachment.pgp
More information about the CMake
mailing list