[CMake] Time Profile our CMake codes

[Michael Jackson]

We do the File IO because we need to store lists of various directories 
for other subprojects and packaging schemes to use. When we first 
developed the CMake codes the "set_property" function was not really 
well developed. I am wondering if using global property lists are a 
better way to go for this.

example:
      get_property(DREAM3DDocRoot GLOBAL PROPERTY DREAM3DDocRoot)

-- 
Mike Jackson  [mike.jackson at bluequartz.net]
> Nicholas Braden <mailto:nicholas11braden at gmail.com>
> May 12, 2016 at 2:06 PM
> I can't answer your question directly, but IIRC opening files on
> Windows is many times more expensive than on other platforms - it
> could be the temp file I/O you are doing.
>
> On Thu, May 12, 2016 at 11:09 AM, Michael Jackson
> Michael Jackson <mailto:mike.jackson at bluequartz.net>
> May 12, 2016 at 12:09 PM
> Is there a way to "time profile" our cmake codes? We have noticed 
> lately that running cmake on our project lately has taken a large 
> uptick in time and we are trying to figure out where the newly added 
> time is coming from. We do a lot of I/O writing temp files, comparing 
> temp files to files that get replaced. We also have a fair number of 
> external libraries that we look for (Boost, Eigen, ITK, VTK, Qt, Qwt, 
> HDF5). If anyone has any ideas we would greatly appreciate it. 
> Although the cmake time on OS X and Linux is not so bad, Windows is 
> getting unbearably slow (even with Ninja/makefiles).
>
> Thanks
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake/attachments/20160512/4da147cf/attachment.html>