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 <jeanmichael.celer...@gmail.com> wrote: > > On Wed, May 10, 2017 at 4:56 PM, Egor Pugin <egor.pu...@gmail.com> 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
