On 6/2/2016 5:29 AM, Alessio wrote:
I'm comparing the following two things:
1. cpack TBZ2 generator
2. "tar cjf" the same files as with cpack. (j option = BZIP2 compression)
I cannot avoid CPack. It takes care of way too many little details of
the packaging. Obviously we use it via lots of install() statements in
our CMakeLists.txt files.
Sounds like it needs some performance testing. One thing to try would
be to compare cmake -E tar with tar and see if it is libtar that is
slow, or something CPack is doing. After that, maybe calgrind or other
tools to profile cpack.
-Bill
--
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
