> Can this use of mixed case-sensitive/all-upper-case can be clarified in the
> documentation for CPACK_ and CPAC_RPM_ component variables?
I was certain that this was already documented... I'll document it and
also change CPackRPM so that it will support both original version of
component name an
Thanks Domen! The use of original-case for in
CPACK_RPM__ was indeed the problem. I never did get the
CPACK_RPM_*_PACKAGE_PREFIX variable to work but I'm using a different
(probably more correct) approach that gets me what I wanted.
Can this use of mixed case-sensitive/all-upper-case can be c
> set(CPACK_GENERATOR "RPM")
> set(CPACK_RPM_BLAH1_USER_BINARY_SPECFILE
> "${CMAKE_CURRENT_SOURCE_DIR}/install/SPECS/blah1.spec.in")
> set(CPACK_RPM_BLAH1_PACKAGE_PREFIX "${CMAKE_INSTALL_PREFIX}/blah1")
> set(CPACK_RPM_BLAH2_PACKAGE_PREFIX "${CMAKE_INSTALL_PREFIX}/blah2")
> set(CPACK_RPM_COMPONENT_
I have the CPack RPM component packager partly working in that it creates
separate RPMs for my two components (soon to be more, but two for now).
However, the RPMs are not quite right because the packager completely
ignores all of my CPACK_RPM__XXX variables, such
as, CPACK_RPM__PACKAGE_PREFIX. The
