Hi Daniel, On Tue, Jun 7, 2016 at 11:27 AM, Daniel Pfeifer <dan...@pfeifer-mail.de> wrote: > On Mon, Jun 6, 2016 at 5:39 PM, Tobias Hunger <tobias.hun...@qt.io> wrote: >> Please help to support your use-cases. > > A while ago I wrote a graphical cache editor in GTK: > https://github.com/purpleKarrot/cmake-gtk > The tool reads the cache and provides a graphical view to modify it. > It can then write the cache, run cmake, and read it back. > > I wanted to see how close we can get to ccmake or cmake-gui without > linking against CMakeLib. > > Here is what I was *unable* to achieve: > * Separating Configure from Generate (two buttons). > * Progress bar. > > Quite a short list, right? > If we have a daemon mode that provides this information (as your > implementation already does), we could let ccmake and cmake-gui use > the daemon instead of linking against CMakeLib.
If the daemon can expose the right information, then you could even be able to write a generator in e.g. python;-) Best Regards, Tobias -- 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
