MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0015217CMakeCPackpublic2014-10-24 02:502016-06-10 14:31
Reportersudakov_ivan 
Assigned ToKitware Robot 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionmoved 
Platformx86-64OSFedora-18OS Version
Product VersionCMake 3.0 
Target VersionFixed in Version 
Summary0015217: CPack make wrong dependencies between components
DescriptionI have three components: a,b,c and code:

install(FILES ${CMAKE_CURRENT_LIST_FILE} DESTINATION /tmp COMPONENT a)
install(FILES ${CMAKE_CURRENT_LIST_FILE} DESTINATION /tmp COMPONENT b)
install(FILES ${CMAKE_CURRENT_LIST_FILE} DESTINATION /tmp COMPONENT c)

SET(CPACK_RPM_a_PACKAGE_REQUIRES "d")
SET(CPACK_RPM_c_PACKAGE_REQUIRES "e")

In result:
 a requires d - ok
 b requires d - wrong
 c requires e - ok

There is the same situation with PROVIDES
Steps To Reproduce
Additional InformationIf I set REQUIRES for ALL components it's work fine:
SET(CPACK_RPM_a_PACKAGE_REQUIRES "d")
SET(CPACK_RPM_c_PACKAGE_REQUIRES "e")
SET(CPACK_RPM_b_PACKAGE_REQUIRES "")
 
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2014-10-24 02:50sudakov_ivanNew Issue
2014-10-24 08:51Eric NOULARDNote Added: 0037072
2016-06-10 14:29Kitware RobotNote Added: 0042650
2016-06-10 14:29Kitware RobotStatusnew => resolved
2016-06-10 14:29Kitware RobotResolutionopen => moved
2016-06-10 14:29Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0037072)
Eric NOULARD   
2014-10-24 08:51   
A wild guess for anyone wanting to handle this:

There isy a leak from one COMPONENT specific value to the other which is not et.

I guess
CPACK_RPM_a_PACKAGE_REQUIRES
sets
CPACK_RPM_PACKAGE_REQUIRES
internally (in CPackRPM.cmake)

but it is not reset when package b is treated?

CPackRPM is "called" for each COMPONENT thus the leak.
(0042650)
Kitware Robot   
2016-06-10 14:29   
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.