Re: [cmake-developers] Splitting CMakeLib
I see, thanks! I'll ping when something is ready, but do not expect much in the near future (2-4 months). On 11 May 2017 at 16:21, Brad King wrote: > On 05/10/2017 10:56 AM, 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? > > Refactoring/organizing/cleanup changes like that would certainly be welcome. > >> 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. > > Stephen Kelly had started work toward separating the code model from the > language. The code model should become an independent representation that > can be input to the generators but be produced independent of the language. > See cmState for example. He isn't working on it anymore but left a thread > some time ago on this list enumerating some future work that could be > picked up by others (I don't recall which thread though). > > -Brad > -- 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
[cmake-developers] CMake 3.9 feature freeze on 2017-06-01
Hi Folks, The feature freeze in 'master' for CMake 3.9 will be on June 1, 2017. I may announce a freeze in 'stage' sometime in the preceding week so that we can get any remaining dashboard trouble cleaned up. 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] Splitting CMakeLib
On 05/10/2017 10:56 AM, 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? Refactoring/organizing/cleanup changes like that would certainly be welcome. > 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. Stephen Kelly had started work toward separating the code model from the language. The code model should become an independent representation that can be input to the generators but be produced independent of the language. See cmState for example. He isn't working on it anymore but left a thread some time ago on this list enumerating some future work that could be picked up by others (I don't recall which thread though). -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] Splitting CMakeLib
On Wed, May 10, 2017 at 4:56 PM, Egor Pugin wrote: > 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? > Strongly in favor. Such a modularization will be a benefit for CMake. It will require to cleanup CMake's internal inter-dependencies and it will help to keep them clean afterwards. It will make CMake's codebase easier to approach by new contributors. It will allow experiments like replacing individual parts (eg. new frontend). Let's learn from LLVM/Clang. > 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) > Don't merge the commands with the command interpreter/vm. 5) Scripting commands 6) Project commands 7) CTest commands 8) Package generators 9) Server ... 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. > Personally, I regard the generators as obsolete and see the future in the server. Cheers, Daniel -- 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
