Re: [cmake-developers] [DISCUSSION] Using COMPONENTs for CMake install(...)?
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 --help-command file > There are a series of resources that have not been specified. > Please look at the files in the folder: > > http://ifw.podsvirov.pro/cmake/dev/unspecified/ > > What components to include these files? Everything in share seems to be about '3rd party integration'. > > For example, files with different licenses? Probably the same component as the Copyright.txt file. Thanks, Steve. -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] [DISCUSSION] Using COMPONENTs for CMake install(...)?
09.12.2014, 23:48, "Brad King" : > 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 long as all three are > required. We already separate the "data" component but it is also > required. Only cmake-gui, ccmake, and the documentation components > are optional. Well. Leave them as separate components and make mandatory. The data now includes subfolders Help, Modules and Templates. Why are Help (the rst set of files)? As they are used after installation? >> I want to clarify: sphinx-man is the documentation that must be >> installed together with tools in Linux? > > No, my comments on that were just to distinguish our use case from > Debian's policy. I think sphinx-man can be just like sphinx-html > except for covering the man-format documentation. It is understandable. >> where can I get NAME and DESCRIPTION for each component? > > Once we identify the final set of components I can help draft the > description text for them. Thank you. > Thanks, > -Brad There are a series of resources that have not been specified. Please look at the files in the folder: http://ifw.podsvirov.pro/cmake/dev/unspecified/ What components to include these files? For example, files with different licenses? And yet. In addition to the list of components must be approved and the list of groups. Regards, Konstantin Podsvirov -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] [DISCUSSION] Using COMPONENTs for CMake install(...)?
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 long as all three are required. We already separate the "data" component but it is also required. Only cmake-gui, ccmake, and the documentation components are optional. > I want to clarify: sphinx-man is the documentation that must be > installed together with tools in Linux? No, my comments on that were just to distinguish our use case from Debian's policy. I think sphinx-man can be just like sphinx-html except for covering the man-format documentation. > where can I get NAME and DESCRIPTION for each component? Once we identify the final set of components I can help draft the description text for them. Thanks, -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] [DISCUSSION] Using COMPONENTs for CMake install(...)?
08.12.2014, 17:26, "Brad King" : > 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. >> Added components: >> - cmake >> - ctest >> - cpack >> - cmake-gui >> - ccmake >> - data >> - sphinx-html >> - sphinx-singlehtml >> - sphinx-qthelp > That looks good, except that "cmake/ctest/cpack" must all be in > one component. Each of those three binaries has logic that assumes > the other two exist. This ground for discussion. By default CPack generators must create one package for each component group. In addition, you can specify whether the component is required and can be specified as any of the components referenced by this component. > There should also be a "sphinx-man group for the man pages. It is not difficult. I will add. I want to clarify: sphinx-man is the documentation that must be installed together with tools in Linux? > Thanks, > -Brad What other components can be identified? I already wrote about this, but where can I get NAME and DESCRIPTION for each component? (something you can find in sphinx documentation, but this is not all). I have some difficulties with the English language and help here would be appropriate. I'm working on a graphical installer (CPack IFW generator), which can install CMake on Windows, Linux and Mac in graphics mode. Graphical installer allows you to acquaint the user with the structure of CMake in the installation process. The installer may include optional components. It is possible to create online installers, where all or some of the components are downloaded and installed as needed. Regards, Konstantin Podsvirov -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] [DISCUSSION] Using COMPONENTs for CMake install(...)?
On 12/07/2014 05:34 PM, Konstantin Podsvirov wrote: > Well, work has started! Good work so far. Please reorganize the commits to have the first one add the install COMPONENT options and the second one add the CPack configuration. > Added components: > - cmake > - ctest > - cpack > - cmake-gui > - ccmake > - data > - sphinx-html > - sphinx-singlehtml > - sphinx-qthelp That looks good, except that "cmake/ctest/cpack" must all be in one component. Each of those three binaries has logic that assumes the other two exist. There should also be a "sphinx-man" group for the man pages. Thanks, -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] [DISCUSSION] Using COMPONENTs for CMake install(...)?
Hi, Brad! 05.12.2014, 22:33, "Brad King" : > 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 data files (modules, templates and documentation) > cmake-doc - extended documentation in various formats for CMake > cmake-qt-gui - Qt4 based user interface for CMake (cmake-gui) I agree. My way of studying operating systems started with Windows and I spend a lot of time here. Then I was introduced to Linux and chose Debian. >> For example: >> -- tools >> - cmake >> - cpack >> - ctest > > Yes. >> -- scripts >> - modules >> - templates > > These are the Debian "cmake-data" package. >> -- documentation >> - manual >> * html version >> * man pages > > Debian packages the tool man pages with the tools due to their > policy of having documentation available for all commands. > Other manuals are in the separate cmake-doc package. For > interactive installers I think we can keep all the docs in > their own separate packages from the tools since the doc > format could be made selectable. It is understandable. > The html and man pages could be placed in separate install > components too. >> -- according to >> - Qt (only necessary) > > Separate components for each of the "ccmake" and "cmake-gui" > interactive dialogs makes sense. > > With the above guidance please go ahead and work on the patch > if you want. All the install() calls will need to be updated > with the proper COMPONENT option(s). I am interested this task. Perhaps I will start working on my server in a separate branch. I will try to create a graphical installers using CPack IFW generator. At first I plan to submit for debugging and testing the compiled version in Debian stable, and Windows 7. Unfortunately I have no way to test this for Mac. :-( Brad what desktop do you use? >> Also I suggest to add in CMakeLists.txt option to control the >> installation of dependencies with CMake >> For example the Qt library. This happens on Windows and Mac >> but I think it is not always necessary in Linux. > > This is a separate task, so let's focus on the components first. > > -Brad Well. A separate task separate from the main :-) Thank you for writing this letter. I was waiting for him. Regards, Konstantin Podsvirov -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] [DISCUSSION] Using COMPONENTs for CMake install(...)?
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 data files (modules, templates and documentation) cmake-doc - extended documentation in various formats for CMake cmake-qt-gui - Qt4 based user interface for CMake (cmake-gui) > For example: > -- tools > - cmake > - cpack > - ctest Yes. > -- scripts > - modules > - templates These are the Debian "cmake-data" package. > -- documentation > - manual > * html version > * man pages Debian packages the tool man pages with the tools due to their policy of having documentation available for all commands. Other manuals are in the separate cmake-doc package. For interactive installers I think we can keep all the docs in their own packages separate from the tools since the doc format could be made selectable. The html and man pages could be placed in separate install components too. > -- according to > - Qt (only necessary) Separate components for each of the "ccmake" and "cmake-gui" interactive dialogs makes sense. With the above guidance please go ahead and work on the patch if you want. All the install() calls will need to be updated with the proper COMPONENT option(s). > Also I suggest to add in CMakeLists.txt option to control the > installation of dependencies with CMake. > For example the Qt library. This happens on Windows and Mac, > but I think it is not always necessary in Linux. This is a separate task, so let's focus on the components first. -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] [DISCUSSION] Using COMPONENTs for CMake install(...)?
Hi, Brad! You always understand me right :-) 03.12.2014, 18:48, "Brad King" : > 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? > > -Brad I wondered at the expense of use of the components. I thought that there might be problems with some CPack generators. Well, that is no problem. The idea of splitting into components appeared when creating a graphical installer for CMake. Although CMake now does not use IFW generator for distribution, I'm working on improving it. 03.12.2014, 23:36, "Brad King" : > On 12/03/2014 03:20 PM, Alexander Neundorf wrote: >> you can use them when calling the cmake_install.cmake manually, instead of >> calling "make install": cmake-DCOMPONENT="MyComponent" -P cmake_install.cmake >> >> I think at least some of the package generators support the components too. > > I don't think the question is about how to use install components > in general, but instead about teaching CMake''s own source tree to > use them. See my response sibling. Yes! In the source tree, you can see some of the components. For example: -- tools - cmake - cpack - ctest -- scripts - modules - templates -- documentation - manual * html version * man pages -- according to - Qt (only necessary) In the graphical installer, the user will be able to see the components of which consists CMake set. The user will not be able to install an optional component, if it is not needed (such as manual). Also I suggest to add in CMakeLists.txt option to control the installation of dependencies with CMake. For example the Qt library. This happens on Windows and Mac, but I think it is not always necessary in Linux. Regards, Konstantin Podsvirov -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] [DISCUSSION] Using COMPONENTs for CMake install(...)?
On 12/03/2014 03:20 PM, Alexander Neundorf wrote: > you can use them when calling the cmake_install.cmake manually, instead of > calling "make install": cmake -DCOMPONENT="MyComponent" -P cmake_install.cmake > > I think at least some of the package generators support the components too. I don't think the question is about how to use install components in general, but instead about teaching CMake's own source tree to use them. See my sibling response. -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] [DISCUSSION] Using COMPONENTs for CMake install(...)?
On Wednesday, December 03, 2014 00:50:52 Konstantin Podsvirov wrote: > 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 redistributable packages. you can use them when calling the cmake_install.cmake manually, instead of calling "make install": cmake -DCOMPONENT="MyComponent" -P cmake_install.cmake I think at least some of the package generators support the components too. Alex -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
Re: [cmake-developers] [DISCUSSION] Using COMPONENTs for CMake install(...)?
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? -Brad -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
[cmake-developers] [DISCUSSION] Using COMPONENTs for CMake install(...)?
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 redistributable packages. Your questions and suggestions! -- Regards, Konstantin Podsvirov -- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake-developers
