I can't reproduce your issue here. (I had to modify your code because
CURRENT_BINARY_DIR was missing the CMAKE_ at its beginning. And since I
modified it anyhow, I added SHOW_PROGRESS and made min req'd be 2.8.3...)
Are you sure you're using 2.8.3 when you see the problem?
Can you repro this on
Hi David,
Am Mittwoch, den 26.01.2011, 08:14 -0500 schrieb David Cole:
From the libarchive source code, it looks like this message appears as
a warning and returns ARCHIVE_WARN.
CMake spits out an error message whenever a libarchive function
returns anything other than ARCHIVE_OK.
Are the time stamps actually restored on extract (when extracting with
CMake and ignoring the warning output)? Or do all files have time of
extraction as their modified times?
On Thu, Jan 27, 2011 at 11:37 AM, Daniel Pfeifer dan...@pfeifer-mail.de wrote:
Hi David,
Am Mittwoch, den 26.01.2011,
Am Donnerstag, den 27.01.2011, 12:48 +0100 schrieb David Cole
david.c...@kitware.com:
On Thu, Jan 27, 2011 at 12:45 PM, Daniel Pfeifer
dan...@pfeifer-mail.de wrote:
Am Donnerstag, den 27.01.2011, 11:42 +0100 schrieb David Cole
david.c...@kitware.com:
Are the time stamps actually restored
Hi,
executing the command 'cmake -E tar xfz archive.tgz' can be really
noisy. It works fine in Linux and also in Windows if I use the Qt GUI to
CMake. In a Windows Terminal it reports CMake Error: Problem with
archive_write_finish_entry(): Can't update time for %s for every single
file
be really
noisy. It works fine in Linux and also in Windows if I use the Qt GUI to
CMake. In a Windows Terminal it reports CMake Error: Problem with
archive_write_finish_entry(): Can't update time for %s for every single
file in the archive.
What is the problem here?
I use CMake 2.8.3
