On 11/10/2014 07:50 PM, SF Markus Elfring wrote:
>> I actually don't know if this is an omission or a deliberate design choice.
> How often do use DEB and RPM package generation with CPack for your software?
>
> Regards,
> Markus
I used it quite often (only rpm), but having said that: I had a need
> I actually don't know if this is an omission or a deliberate design choice.
How often do use DEB and RPM package generation with CPack for your software?
Regards,
Markus
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://www.cmake.org/Wiki/CMake_F
> You could, as a workaround for the problem, define a add_custom_target
> that removes the corresponding rpm/deb packages and just calls 'cmake
> --build --target package' to regenerate them.
Thanks for your suggestion.
> It's not an ideal solution, but it worked just fine for me.
Does this fe
On 11/10/2014 07:40 PM, SF Markus Elfring wrote:
>> You could, as a workaround for the problem, define a add_custom_target
>> that removes the corresponding rpm/deb packages and just calls 'cmake
>> --build --target package' to regenerate them.
> Thanks for your suggestion.
>
>
>> It's not an ideal
On 11/09/2014 08:34 PM, SF Markus Elfring wrote:
> Hello,
>
> I configured a specific software to use the CPack modules to generate
> corresponding DEB and RPM packages together with CMake 3 a while ago.
>
> I notice now that package specifications and control files contain
> outdated version data
Hello,
I configured a specific software to use the CPack modules to generate
corresponding DEB and RPM packages together with CMake 3 a while ago.
I notice now that package specifications and control files contain
outdated version data after I called the command "make package".
How can I achieve
