Konstantin Podsvirov wrote:
The data now includes subfolders Help, Modules and Templates.
Why are Help (the rst set of files)? As they are used after installation?
Yes. The Help files need to be mandatory too. They are used by cmake for
showing documentation on the command line like
cmake
08.12.2014, 17:26, Brad King brad.k...@kitware.com:
On 12/07/2014 05:34 PM, Konstantin Podsvirov wrote:
Well, work has started!
Good work so far.
I tried :-)
Please reorganize the commits to have the first one add the install
COMPONENT options and the second one add the CPack configuration.
On 12/9/2014 1:39 PM, Konstantin Podsvirov wrote:
That looks good, except that cmake/ctest/cpack must all be in
one component.
specify whether the component is required and can be specified as
any of the components referenced by this component.
I suppose they can be separate components as
On 12/04/2014 12:59 AM, Konstantin Podsvirov wrote:
In the source tree, you can see some of the components.
The Debian packaging can serve as a good reference:
cmake - cross-platform, open-source make system
cmake-curses-gui - curses based user interface for CMake (ccmake)
cmake-data - CMake
Hi, Brad!
05.12.2014, 22:33, Brad King brad.k...@kitware.com:
On 12/04/2014 12:59 AM, Konstantin Podsvirov wrote:
In the source tree, you can see some of the components.
The Debian packaging can serve as a good reference:
cmake - cross-platform, open-source make system
cmake-curses-gui -
On 12/02/2014 04:50 PM, Konstantin Podsvirov wrote:
The command install(...) allows you to specify the COMPONENT.
Why this feature is not used by CMake?
It simply never came up before. There is no reason not to
define components for CMake's installation. What set of
components do you propose?
CMake is being developed for a long time, but does not use COMPONENTs during
installation. Why?
The command install(...) allows you to specify the COMPONENT. Why this feature
is not used by CMake?
Is it possible to split the install CMake on COMPONENTs? Further it can be used
when creating
