On Tue, Jul 05, 2016 at 21:01:36 +0300, Ruslan Baratov wrote: > Well it's never too late to learn something new. Also `tar` is not > widely used on Windows so to write nice code you should convert it to > `cmake -E tar`. That the whole point of `cmake -E` feature. > I don't see the problem here, it was used internally, unpack archive for > you and you can do what you want with **unpacked** sources. Anyway you > can always force the name with |DOWNLOAD_NAME.|
I'm more considering the case of using the files as they exist on the disk for other purposes, not necessarily through code (which probably should be using `cmake -E tar`). For example, I will do: - tar xf $tarball.tar.gz - cp -a $tarball $tarball.to-patch - $edit .to-patch - diff -U5 -r $tarball $tarball.to-patch to create patches for ExternalProject tarballs we use. --Ben -- 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
