Closed otheus closed 8 years ago
How can we get CPACK_PACKAGE_FILE_NAME
to use the canonical {name}-{major}.{minor}.{release}-{vendor}.{vendorrelease}-{arch}
?
cpack -G RPM -R 2 --vendor UIBK
should work, but no.
Something is really wrong with how the CpackConfig.make file is configured. Options on the command line to cpack should override them. In the end, I hardcoded my values in CPackConfig.cmake
but that seems like a Hack.
Hello,
Can someone update the README so as to demonstrate how to make and configure such variables with cpack?
It is already in README.md. Please look at this. Also, you can prepare a pull request with your changes.
How can we get CPACK_PACKAGE_FILE_NAME to use the canonical
cpack documentation says that you should override next options: ${CPACK_PACKAGE_NAME} ${CPACK_PACKAGE_VERSION} ${CPACK_SYSTEM_NAME}. They may be specified during configuration step.
cpack -G RPM -R 2 --vendor UIBK
should work, but no.
My patch 89bcc1c fixes hard-coded vendor property of rpm file and updates links in README.md. Now you can override vendor from command line option. The default value is the same "EPAM Systems" as before.
generally, if you want to hack something - you have to do it yourself.
The tool ld-config can help you to configure your ld.so to look in correct directory for analysis modules
Is there any way to make the build process more harmonious with the RPM packaging process? The
cpack -G RPM
puts the shared analysis modules into/usr/lib/nfstrace
, which one would expect on a RHEL system. But the cmake used the default/usr/local
as a prefix. Can someone update the README so as to demonstrate how to make and configure such variables with cpack?