[cmake-developers] cmake install command expected performance?

[Robert Goulet]

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.king at kitware.com] 
Sent: Tuesday, February 24, 2015 9:57 AM
To: Robert Goulet; Joshua Clayton
Cc: cmake-developers at 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