I've accidentally dropped the mailing list in reply:
> I do not find an example on how to provide separate RPM's
> for them; one for the binary and one for the headers+library.
> The required results (rough example):
>
> - foo-1.2.3.4-1.x86_64.rpm
> - libfoo-1.2.3.4-1.x86.64.rpm
You have to provi
Hm I've accidentally dropped cmake mailing list when replying
before... Sorry about that.
> Im using "bin" and "devel" as component names. I tried next with upper and
> lower case in the properties but no difference.
> it's about what you see in the RPM header using "rpm -qlip name.rpm" ...
Compo
Hi Thomas,
CPack RPM may generate several packages at once if you define COMPONENTS in
your project.
The behavior of CPackRPM w.r.t. COMPONENT packaging depends on
Some CPack COMPONENT generic variables, namelly:
CPACK_RPM_COMPONENT_INSTALL --> this one must be set to ON
CPACK_COMPONENTS_* varia
Hi,
We are currently looking forward to migrate to CMake and
we are struggling a bit with cpack.
The first project we migrate provides a executable binary but also
a library and its headers.
I do not find an example on how to provide separate RPM's
for them; one for the binary and one for the he
