You're right. It was partly because I had my build tree as a subdirectory of my source tree. Just used to that from autotools. I also failed to ignore my .git directory, which also contributed to the slowness. With both fixed, the speed and tarball size are fine.
Thanks On Tue, Sep 18, 2012 at 1:27 AM, Eric Noulard <[email protected]>wrote: > 2012/9/18 Jack Stalnaker <[email protected]>: > > Hi, > > > > I'm not sure what I'm doing wrong, but when I run cpack --config > CPackSourceConfig.cmake -G TGZ, the operation runs forever and produces > archives on the order of dozens of gigabytes. As far as cpack goes, I don't > have much specified other than include(cpack) and the version variables. > > May be you could send us your "CPackSourceConfig.cmake" ? > > > I do have include(InstallRequiredSystemLibraries) as well, but that's > pretty much it. > > Which version of CPack are you using? > On which platform (Windows? Linux? ...) > > > > I did some investigation, and the problem was pretty easy to spot. > Inside the generated _CPack* directory was the installed source directory, > which in turn had a nested copy of the same source directory, etc, down > many, many levels, so that many gigabytes of disc space were consumed. I'm > sorry if this isn't specific enough, but does anyone know what's going on? > > Is your build tree inside the source tree, i.e. the build directory is > a sub-directory > of the build tree? > > Do you set CPACK_SOURCE_IGNORE_FILES to any values > in your CMakeLists.txt? > > > Does the problem with other generator like zip ? > > -- > Erk > Le gouvernement représentatif n'est pas la démocratie -- > http://www.le-message.org >
-- Powered by www.kitware.com Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Follow this link to subscribe/unsubscribe: http://www.cmake.org/mailman/listinfo/cmake
