MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0008769CMakeCPackpublic2009-03-19 11:372016-06-10 14:30
ReporterDerek Bruening 
Assigned ToBill Hoffman 
PrioritynormalSeverityfeatureReproducibilityalways
StatusclosedResolutionmoved 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0008769: support different name for CPack tarball versus its top-level tar directory
DescriptionI want my tarball to have a different name than its top-level directory.
E.g., I want my tarball to expand to foo/ but be named Foo-Linux-1.3.3.tgz.

It seems that this is not supported: while there are a billion CPack variables
that claim to be the "install directory name", the only one that is
actually used is CPACK_PACKAGE_FILE_NAME, which is also the name of the
tarball: so I can't separate them.

Looks like cmCPackGenerator::PrepareNames() in
CMake/Source/CPack/cmCPackGenerator.cxx sets up the
temp dir and uses CPACK_PACKAGE_FILE_NAME: so can't be changed.

Perhaps I could add the foo/ layer during install and then
SET(CPACK_INCLUDE_TOPLEVEL_DIRECTORY 0) but I use my install
directories locally and don't want an extra layer there.

By setting CPACK_PACKAGE_FILE_NAME to foo/ and then hacking presumably internal CPack variables like CPACK_TEMPORARY_PACKAGE_FILE_NAME I can get something like what I want but I have to hardcode the tarball file extension.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-03-19 11:37Derek BrueningNew Issue
2009-03-22 21:57Bill HoffmanStatusnew => assigned
2009-03-22 21:57Bill HoffmanAssigned To => Bill Hoffman
2016-06-10 14:27Kitware RobotNote Added: 0041520
2016-06-10 14:27Kitware RobotStatusassigned => resolved
2016-06-10 14:27Kitware RobotResolutionopen => moved
2016-06-10 14:30Kitware RobotStatusresolved => closed

Notes
(0041520)
Kitware Robot   
2016-06-10 14:27   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.