[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-kuml-devel
Subject:    Re: Kuml library module testing, project build time
From:       Darius Stachow <dstachow () ngi ! de>
Date:       2000-07-10 22:21:27
[Download RAW message or body]

Hey Keith,

On Mon, 10 Jul 2000, you wrote:
>Hi,
>
>At the moment I believe that there is no specific method for testing
>modules within libraries - ie liblines.a . Just an idea but is there an
>easy was to provide a 'Testing' menu to test modules of interest?
Adding a new menu shouldn't be a big deal.
Just take a look at the file kuml.cpp [KumlApp] in method initMenubar() and 
statusCallback().



>Also I was wondering if there is a way to speed up the building of Kuml
>when changes have been made to a library?Is there a option to pass to
>configure that may help?
Normally just the modified files and all files that depends on them should be 
compiled again. And so they do on my system ;-)

But, yes, the build time for kuml is high :-(
Even on my new athlon 700 (256mb) a complete build with debug information on
lasts round about 17 minutes :-(

The available computers a mortal human can afford are still much too slow :-(
I would like to have a super computer that build the complete project 
within 5 seconds or so ;-)

-----------------------------------------------------------------
Darius Stachow          e-mail  dstachow@ngi.de
Borgfelder Str. 16              stacho_d@informatik.fh-hamburg.de
20537 Hamburg
Germany

[prev in list] [next in list] [prev in thread] [next in thread]