On 3/21/19 2:19 PM, Eric Noulard wrote: > Can any CMake developer that has been participating in this new > file api shed some light on the rational of this foreseen switch? > I'm just curious about it. What was wrong/problematic with server mode? > Does the new file api solves some IDE integration issue?
The file-api approach does not require a long-running CMake server process and the associated memory consumption. It also offers a better story for format evolution (versioned queries, versioned replies). The main improvement in the reported codemodel is the availability of backtraces. The tracking issue is here: * https://gitlab.kitware.com/cmake/cmake/issues/18398 Issues that led to it include: * https://gitlab.kitware.com/cmake/cmake/issues/17753 * https://gitlab.kitware.com/cmake/cmake/issues/17539 -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: https://cmake.org/mailman/listinfo/cmake-developers
