[Insight-developers] No longer building XCode
Bill Hoffman
bill.hoffman at kitware.com
Tue Aug 30 13:00:53 EDT 2011
On 8/29/2011 5:37 PM, Bradley Lowekamp wrote:
> Hello,
>
> I modified the CTest script to not add any additional warning flags, so
> the FLAGS are just empty now. I fired it off at about 3pm and it's still
> going, it's not producing a heck of a lot of warning, but it is up to
> 9400K of output. This appears to indicate that it's not related to the
> amount of warninga produced, but doesn't rule out an increase in the
> amount of time spent parsing the output.
>
> Also looking at the graph linked below, I don't see a correlation with
> the number of warning and the increase time to build ITK.
>
> If it is spending a lot of time parsing the output, I should check to
> ensure that my cmake was built in release mode. That will be the
> experiment for tomorrow. I would be surprised if lack of cmake
> optimization would cause 3X in crease in build time. I still think the
> modularization may not be playing well with XCode.
>
Did the Experimental ever finish?
The non-optimized cmake might be that much slower. It is doing lots of
stl string stuff, which in debug or non-optimized mode can be very slow.
However, I suspect it is just the shear volume of output that is
causing the trouble.
Xcode is very very verbose, and CMake looks at every line of output. I
will investigate some more and see if there is something that can be done...
-Bill
More information about the Insight-developers
mailing list