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
--
Mike Jackson [mike.jack...@bluequartz.net]
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_FAQ
Kitware offers various services to support the CMake community. For more
information on each offering, please visit:
CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake
