Re: [cmake-developers] Splitting CMakeLib

2017-05-23 Thread Nagy-Egri Máté Ferenc via cmake-developers
Developers Tárgy: 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

Re: [cmake-developers] Splitting CMakeLib

2017-05-11 Thread Egor Pugin
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

Re: [cmake-developers] Splitting CMakeLib

2017-05-11 Thread Brad King
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. >

Re: [cmake-developers] Splitting CMakeLib

2017-05-11 Thread Daniel Pfeifer
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 benefi

Re: [cmake-developers] Splitting CMakeLib

2017-05-10 Thread Egor Pugin
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 subdirectorie

Re: [cmake-developers] Splitting CMakeLib

2017-05-10 Thread Jean-Michaël Celerier
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 Kitw

Re: [cmake-developers] Splitting CMakeLib

2017-05-10 Thread Egor Pugin
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 >> f

Re: [cmake-developers] Splitting CMakeLib

2017-05-10 Thread Ben Boeckel
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

[cmake-developers] Splitting CMakeLib

2017-05-10 Thread Egor Pugin
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 lib