The way this is going, is to continue with one package rather than use a workaround, if we have some idea if/when CPACK_COMPONENT_<compName>_DEPENDS will be implemented. But, am I understanding correctly that CPACK_COMPONENT_<compName>_DEPENDS isn't expected to work? I see some CMake examples that use it so I'm confused why this works for some people.
I guess my question now is, is there a plan to make the CPACK_COMPONENT_<compName>_DEPENDS mechanism work? At the risk of being asked to contribute :), is there any way to know when? My group can make a decision based on that info.
Thank you greatly!
Jeff
<turkey here>
On Wed Nov 20 4:09 , Jeremy Fix
On 11/20/2013 09:52 AM, Eric Noulard wrote:
> 2013/11/20 Jeremy Fix <jeremy....@supelec.fr>:
>> Hello,
>>
>> I'm surprised CPACK_RPM_gui_PACKAGE_REQUIRES works , I don't find any use of
>> CPACK_RPM__REQUIRES in CPackRPM.cmake;
>
> Yes there is for all
>
> URL REQUIRES SUGGESTS PROVIDES OBSOLETES PREFIX CONFLICTS AUTOPROV
> AUTOREQ AUTOREQPROV
>
> see lines 555 and following we check for component specific value first:
>
> if(DEFINED CPACK_RPM_${CPACK_RPM_PACKAGE_COMPONENT}_PACKAGE_${_RPM_SPEC_HEADER})
>
> then
> else()
> if(DEFINED CPACK_RPM_PACKAGE_${_RPM_SPEC_HEADER})
>
> However we may have check the definition of
> "CPACK_COMPONENT__DEPENDS" first
> in order to fill-in CPACK_RPM__REQUIRES.
> This is not done.
>
> Moreover I'm not sure this could be easily factoired out since the
> syntax for dependency specification
> may well be package type specific (different name or syntax for DEB or
> RPM for example).
>
>> What I can suggest you for generating several packages with different
>> dependencies is to generate the different packages in multiple steps. If we
>> suppose you defined 2 components (in the INSTALL commands) called : binary
>> and devel ,you can then generate the packages (whether deb or rpm) as
>> follows:
>>
>>
>> SET(CPACK_INSTALL_CMAKE_PROJECTS "${CMAKE_BINARY_DIR};${CMAKE_PROJECT_NAME};
>> ${MYBUILDTYPE};/")
>>
>> then for the dependencies:
>>
>> IF(MYBUILDTYPE STREQUAL "binary")
>> SET(CPACK_RPM_PACKAGE_REQUIRES "gsl")
>> SET(CPACK_DEBIAN_PACKAGE_DEPENDS "libgsl0-dev")
>> ELSE()
>> SET(CPACK_RPM_PACKAGE_REQUIRES "gsl-devel")
>> SET(CPACK_DEBIAN_PACKAGE_DEPENDS "libgsl0-dev")
>> ENDIF()
>>
>>
>> Then the packages are generated with:
>>
>> cmake -DMYBUILDTYPE="binary" && make package
>> cmake -DMYBUILDTYPE="devel" && make package
>
> You should be able to do that with component packaging and a
> CPACK_PROJECT_CONFIG_FILE.
>
I'm not familiar with CPACK_PROJECT_CONFIG_FILE;
I had issues with the package names generated with component packaging
as the component name is added at the end of the package name; I
prefered to generate the components in two steps to tweak the
CPACK_RPM_PACKAGE_NAME and I use some commands a bit more complicated
than the above;
IF(MYBUILDTYPE STREQUAL "binary")
SET(CPACK_RPM_PACKAGE_NAME ${CMAKE_PROJECT_NAME})
SET(CPACK_DEBIAN_PACKAGE_NAME ${CMAKE_PROJECT_NAME})
SET(CPACK_PACKAGE_FILE_NAME
${CMAKE_PROJECT_NAME}-${PACKAGE_VERSION}-${CMAKE_SYSTEM_PROCESSOR})
SET(CPACK_INSTALL_CMAKE_PROJECTS
"${CMAKE_BINARY_DIR};${CMAKE_PROJECT_NAME};binary;/")
ELSEIF(MYBUILDTYPE STREQUAL "devel")
SET(CPACK_RPM_PACKAGE_NAME ${CMAKE_PROJECT_NAME}-devel)
SET(CPACK_DEBIAN_PACKAGE_NAME ${CMAKE_PROJECT_NAME}-devel)
SET(CPACK_PACKAGE_FILE_NAME
${CMAKE_PROJECT_NAME}-devel-${PACKAGE_VERSION}-${CMAKE_SYSTEM_PROCESSOR})
SET(CPACK_INSTALL_CMAKE_PROJECTS
"${CMAKE_BINARY_DIR};${CMAKE_PROJECT_NAME}-devel;devel;/")
ENDIF()
This is just to ensure consistency between the field "Name:" in the
autogenerated spec file is : pkg and pkg-devel ;
and the generated RPM (or deb) filenames: pkg-1.00-i686.rpm and
pkg-devel-1.00-i686.rpm
jeremy.
--
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://www.cmake.org/mailman/listinfo/cmake
-- 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://www.cmake.org/mailman/listinfo/cmake
