2013/11/27 :
> What an honor for me that you guys responded so quickly. Our group has done
> well to move to CMake. Sorry for taking such a long time to reply; I'm part
> of a big organization that can be slow to decide things.
>
> The way this is going, is to continue with one package rather than
What an honor for me that you guys responded so quickly. Our group has done well to move to CMake. Sorry for taking such a long time to reply; I'm part of a big organization that can be slow to decide things.
The way this is going, is to continue with one package rather than use a workaround, if
On 11/20/2013 09:52 AM, Eric Noulard wrote:
2013/11/20 Jeremy Fix :
Hello,
I'm surprised CPACK_RPM_gui_PACKAGE_REQUIRES works , I don't find any use of
CPACK_RPM__REQUIRES in CPackRPM.cmake;
Yes there is for all
URL REQUIRES SUGGESTS PROVIDES OBSOLETES PREFIX CONFLICTS AUTOPROV
AUTOREQ AUTOR
2013/11/20 Jeremy Fix :
> Hello,
>
> I'm surprised CPACK_RPM_gui_PACKAGE_REQUIRES works , I don't find any use of
> CPACK_RPM__REQUIRES in CPackRPM.cmake;
Yes there is for all
URL REQUIRES SUGGESTS PROVIDES OBSOLETES PREFIX CONFLICTS AUTOPROV
AUTOREQ AUTOREQPROV
see lines 555 and following we c
Hello,
I'm surprised CPACK_RPM_gui_PACKAGE_REQUIRES works , I don't find any
use of CPACK_RPM__REQUIRES in CPackRPM.cmake;
What I can suggest you for generating several packages with different
dependencies is to generate the different packages in multiple steps. If
we suppose you defined 2 c
Hello CMake group,
I'm trying to do a component-based install that will produce multiple packages, where one package depends on another. I am using cmake version 2.8.12.1. Have multiple packages working well but the dependencies have not been easy.
The variable CPACK_COMPONENT__DEPENDS, given by
