[Insight-developers] Long CMake configuration time on Windows?

Cory Quammen cquammen at cs.unc.edu
Fri Sep 16 11:22:37 EDT 2011


On Fri, Sep 16, 2011 at 11:16 AM, David Cole <david.cole at kitware.com> wrote:
> 1st configures of ITK with Visual Studio typically take on the order
> of 5 to 7 minutes, with each try_compile operation taking on the order
> of 1 second.
>
> Over an hour total and 10 seconds each is indeed very slow...
>
> Do you happen to have a virus checker installed that's analyzing files
> in the build tree as they're being produced?

I do have a virus checker enabled. I'll rerun with it off and report
the results.

Cory

>
>
> On Fri, Sep 16, 2011 at 11:09 AM, Cory Quammen <cquammen at cs.unc.edu> wrote:
>> Hi all,
>>
>> Yesterday I configured ITK from the latest git master with CMake on
>> Windows 7 with Visual Studio 9 as the compiler.
>>
>> The initial configuration step in CMake took over an hour! Each of the
>> tests for the existence of headers and type size checks take about 10
>> seconds to run, and there are many such tests.
>>
>> Is anyone else seeing this, or is my system particularly slow? I have
>> a new laptop with a quad core i7. On the same laptop running Ubuntu in
>> a VirtualBox VM with a Windows 7 host system, configuration takes a
>> minute or two at most.
>>
>> Thanks,
>> Cory
>>
>> --
>> Cory Quammen
>> Research Associate
>> Department of Computer Science
>> The University of North Carolina at Chapel Hill
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Kitware offers ITK Training Courses, for more information visit:
>> http://kitware.com/products/protraining.html
>>
>> Please keep messages on-topic and check the ITK FAQ at:
>> http://www.itk.org/Wiki/ITK_FAQ
>>
>> Follow this link to subscribe/unsubscribe:
>> http://www.itk.org/mailman/listinfo/insight-developers
>>
>



-- 
Cory Quammen
Research Associate
Department of Computer Science
The University of North Carolina at Chapel Hill


More information about the Insight-developers mailing list