MantisBT - CMake
View Issue Details
0013015CMakeCPackpublic2012-03-04 04:472016-06-10 14:21
Andrew Aladjev 
Domen Vrankar 
normalfeaturealways
closedfixed 
LinuxDebianwheezy
CMake 2.8.5 
CMake 3.6 
0013015: cpack deb generator components specify output names
http://stackoverflow.com/questions/9538642/cpack-deb-generator-components-output-names [^]
install (TARGETS ${PROJECT_NAME}_shared DESTINATION ${CMAKE_INSTALL_PREFIX}/lib
        COMPONENT runtime)
    install (TARGETS ${PROJECT_NAME}_static DESTINATION ${CMAKE_INSTALL_PREFIX}/lib
        COMPONENT development)
    install (FILES ${INCLUDES} DESTINATION ${CMAKE_INSTALL_PREFIX}/include
        COMPONENT development)

    ...
    set (CPACK_PACKAGE_FILE_NAME
        "lib${CPACK_PACKAGE_NAME}_${CPACK_PACKAGE_VERSION}_${CPACK_DEBIAN_PACKAGE_ARCHITECTURE}")

I have 2 deb packages as a result:

    libmpreal_0.1.1-1_amd64-development.deb
    libmpreal_0.1.1-1_amd64-runtime.deb

But I want to have for debian standarts another names:

    libmpreal-dev_0.1.1-1_amd64.deb
    libmpreal_0.1.1-1_amd64.deb
Now I am reading [this][1] at the method **cmCPackDebGenerator::PackageOnePack**
here is a code:

    outputFileName(
        std::string(this->GetOption("CPACK_PACKAGE_FILE_NAME"))
        + "-" + packageName + this->GetOutputExtension()
    );

Does this mean that I cant specify a name for my packages?! I would like to make a mistake..


  [1]: https://github.com/Kitware/CMake/blob/master/Source/CPack/cmCPackDebGenerator.cxx [^]
No tags attached.
related to 0012997closed Kitware Robot Provide a more flexible way to name package produced by CPack 
related to 0015042closed Kitware Robot Add CPACK_PACKAGE_COMPONENT_NAME that naming component packages gets more flexible 
Issue History
2012-03-04 04:47Andrew AladjevNew Issue
2012-03-04 10:06Eric NOULARDRelationship addedrelated to 0012997
2012-03-04 10:10Eric NOULARDNote Added: 0028805
2012-08-11 21:35David ColeStatusnew => backlog
2012-08-11 21:35David ColeNote Added: 0030422
2014-07-28 09:26Nils GladitzRelationship addedrelated to 0015042
2016-05-17 18:40Domen VrankarAssigned To => Domen Vrankar
2016-05-17 18:40Domen VrankarStatusbacklog => assigned
2016-05-17 18:43Domen VrankarNote Added: 0041068
2016-05-17 18:43Domen VrankarStatusassigned => resolved
2016-05-17 18:43Domen VrankarFixed in Version => CMake 3.6
2016-05-17 18:43Domen VrankarResolutionopen => fixed
2016-06-10 14:21Kitware RobotNote Added: 0041171
2016-06-10 14:21Kitware RobotStatusresolved => closed

Notes
(0028805)
Eric NOULARD   
2012-03-04 10:10   
Currently the package naming scheme for component package
are not as flexible as you want.
This is not specific to DEB generator
see the related bug 0012997 and reference therein.

Currently you cannot do what you want.
I should be working on this but I'm not sure I'll be able to do this before
2.8.8 (any help would be welcome).
(0030422)
David Cole   
2012-08-11 21:35   
Sending old, never assigned issues to the backlog.

(The age of the bug, plus the fact that it's never been assigned to anyone means that nobody is actively working on it...)

If an issue you care about is sent to the backlog when you feel it should have been addressed in a different manner, please bring it up on the CMake mailing list for discussion. Sign up for the mailing list here, if you're not already on it: http://www.cmake.org/mailman/listinfo/cmake [^]

It's easy to re-activate a bug here if you can find a CMake developer who has the bandwidth to take it on, and ferry a fix through to our 'next' branch for dashboard testing.
(0041068)
Domen Vrankar   
2016-05-17 18:43   
CPackDEB now generates packages with deb standard package names:

https://cmake.org/gitweb?p=cmake.git;a=commit;h=3a55a0e [^]
https://cmake.org/gitweb?p=cmake.git;a=commit;h=316dd61 [^]
(0041171)
Kitware Robot   
2016-06-10 14:21   
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.