Re: [cmake-developers] Splitting CMakeLib
It's not the question of WPO. Some bottom components from my list involve unwanted dependencies like flex/bison, curl etc. Also I don't like building those other files. At the end cmakelib is very fat itself, it can be very useful to split it into light, observable components, move to subdirectories, maybe choose possible public apis. On 10 May 2017 at 19:09, Jean-Michaël Celerier wrote: > > On Wed, May 10, 2017 at 4:56 PM, Egor Pugin wrote: >> >> but CMakeLib looks too fat. > > > > In this age of link-time whole-program optimizations is this really a > problem ? -- Egor Pugin -- 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] Splitting CMakeLib
On Wed, May 10, 2017 at 4:56 PM, Egor Pugin wrote: > but CMakeLib looks too fat. In this age of link-time whole-program optimizations is this really a problem ? -- 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] Splitting CMakeLib
I'd like to replace cmake language (frontend) with something different. So, I need only target and generators. On 10 May 2017 at 18:11, Ben Boeckel wrote: > On Wed, May 10, 2017 at 17:56:07 +0300, Egor Pugin wrote: >> I'd like to re-use some CMake internal components, but CMakeLib looks too >> fat. >> Is it possible to split it into several libraries? Are such changes >> welcome to contribute? > > What is the use case? CMake does not ship an SDK to link against, so > presumably this is something going into CMake itself? > > --Ben -- Egor Pugin -- 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] Splitting CMakeLib
On Wed, May 10, 2017 at 17:56:07 +0300, Egor Pugin wrote: > I'd like to re-use some CMake internal components, but CMakeLib looks too fat. > Is it possible to split it into several libraries? Are such changes > welcome to contribute? What is the use case? CMake does not ship an SDK to link against, so presumably this is something going into CMake itself? --Ben -- 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] Splitting CMakeLib
Hi! I'd like to re-use some CMake internal components, but CMakeLib looks too fat. Is it possible to split it into several libraries? Are such changes welcome to contribute? Some rough plan: 1) Support library (if any stuff) 2) Core library (targets etc.) 3) Generators library 4) CMake syntax library (lexer, parser) 5) Commands implementation library (could be merged with 4) True cmake power is in its generators. It's always possible to rip off all other stuff, but in order to be tied with mainstream and contribute back, I'm asking this. -- Egor Pugin -- 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
