Hello, Sorry for reviving an old thread (https://cmake.org/pipermail/cmake/2013-December/056517.html) but it seems to have died without a proper answer, at least one that I could find.
I'd like to offer an additional reason why CMAKE_EXPORT_COMPILE_COMMANDS would be beneficial if on by default, one that apparently didn't come up. IDEs like KDevelop and QtCreator use this option to know the layout/contents of a project. They will add it to the cmake invocation when you create a new build directory for said project. However, they can also be pointed to an already existing build directory, in which case it'd be preferable if they didn't have to run cmake again (neither IDE has the option to run cmake under the kind of strictly controlled environment that might be required to configure it "just right"). Regards, René -- 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
