cpsauer created this revision. cpsauer added a reviewer: sammccall. cpsauer created this object with visibility "All Users". Herald added subscribers: usaxena95, kadircet. cpsauer requested review of this revision. Herald added subscribers: cfe-commits, ilya-biryukov. Herald added a project: clang.
This doc lists ways of getting compilation databases out of some popular build systems for use with clangd and other tooling. We built such a way for Bazel and just released it after a bunch of requests on GitHub. Thought I should propose that we add a link to help people find it and use clang tooling. (This is my first revision submitted via LLVM Phabricator, so if I've messed something up, I'd really appreciate your help and patience. Asking for a review from Sam McCall, because I've had a great time working with him elsewhere on GitHub before and because I saw him in the Git history for this file.) Repository: rG LLVM Github Monorepo https://reviews.llvm.org/D114213 Files: clang/docs/JSONCompilationDatabase.rst Index: clang/docs/JSONCompilationDatabase.rst =================================================================== --- clang/docs/JSONCompilationDatabase.rst +++ clang/docs/JSONCompilationDatabase.rst @@ -36,6 +36,12 @@ For projects on Linux, there is an alternative to intercept compiler calls with a tool called `Bear <https://github.com/rizsotto/Bear>`_. +`Bazel <https://bazel.build>`_ can export a compilation database via +`this extractor extension +<https://github.com/hedronvision/bazel-compile-commands-extractor>`_. +Bazel is otherwise resistant to Bear and other compiler-intercept +techniques. + Clang's tooling interface supports reading compilation databases; see the :doc:`LibTooling documentation <LibTooling>`. libclang and its python bindings also support this (since clang 3.2); see
Index: clang/docs/JSONCompilationDatabase.rst =================================================================== --- clang/docs/JSONCompilationDatabase.rst +++ clang/docs/JSONCompilationDatabase.rst @@ -36,6 +36,12 @@ For projects on Linux, there is an alternative to intercept compiler calls with a tool called `Bear <https://github.com/rizsotto/Bear>`_. +`Bazel <https://bazel.build>`_ can export a compilation database via +`this extractor extension +<https://github.com/hedronvision/bazel-compile-commands-extractor>`_. +Bazel is otherwise resistant to Bear and other compiler-intercept +techniques. + Clang's tooling interface supports reading compilation databases; see the :doc:`LibTooling documentation <LibTooling>`. libclang and its python bindings also support this (since clang 3.2); see
_______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits