Yes comparing timestamp is the way to go, but why is it so slow in cmake? I added command to set it to lazy report and it saved 1 second. So it's something else... I forgot to mention that there's a weird pause at the end after installing all files... not sure what it's doing. It looks like this part is taking the most amount of time.
-----Original Message----- From: Brad King [mailto:brad.k...@kitware.com] Sent: Tuesday, February 24, 2015 9:57 AM To: Robert Goulet; Joshua Clayton Cc: cmake-developers@cmake.org Subject: Re: [cmake-developers] cmake install command expected performance? On 02/24/2015 09:51 AM, Robert Goulet wrote: > takes 50+ seconds for cmake to realize that all files don't need to be > copied It's comparing the time stamps of every corresponding file. On many filesystems that is faster than the actual copy. > Perhaps the log spam for every file in the console is part of the problem? > Is there a way to turn it off? http://www.cmake.org/cmake/help/v3.1/variable/CMAKE_INSTALL_MESSAGE.html set(CMAKE_INSTALL_MESSAGE LAZY) -Brad -- 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-developers
