Unfortunately it would take more than one run of CPack, but you may
find useful something like:
in CMakeLists.txt:
set( CPACK_PROJECT_CONFIG_FILE
"${CMAKE_CURRENT_SOURCE_DIR}/CMakeCPackOptions.cmake" )
in CMakeCPackOptions.cmake:
set( CPACK_PACKAGE_FILE_NAME "${CPACK_PACKAGE_NAME}" )
which woul
On 01/29/2015 11:24 PM, Iosif Neitzke wrote:
Where for a single run of CPack, each component name produces a
corresponding named .deb file or ...?
Yes. Exactly.
Have you tried using CPACK_PROJECT_CONFIG_FILE [0]? This allows you
to set a few options at packaging time which can change the final
Where for a single run of CPack, each component name produces a
corresponding named .deb file or ...?
Have you tried using CPACK_PROJECT_CONFIG_FILE [0]? This allows you
to set a few options at packaging time which can change the final
output package file name.
[0] http://www.cmake.org/cmake/hel
All,
I'm trying to have CPack create filenames in the debian-conformant
format using my component definitions.
It looks like there was an issue in place to resolve this (0012997) by
exposing a CPACK_COMPONENT_NAME variable, but it doesn't look like it
was ever resolved/committed.
Is there
