On 03/02/2016 04:36 AM, Richard Wiedenhöft wrote: > The way I see it there is no downside to this and it spares me (and > hopefully others) from polluting my CMakeLists.txt with > "set(CMAKE_EXPORT_COMPILE_COMMANDS ON)" making them more readable.
The down side is it takes longer to generate and not everyone wants the rules, especially in very large projects with lots of compilations. There is ongoing discussion in other threads about improved IDE and tooling integration. In the long run that work will eliminate the need for this option altogether. -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
