From d0b6cd6d9addda17fc57e164829aeae13b0cf0e8 Mon Sep 17 00:00:00 2001 From: Andrey Bokhanko Date: Fri, 19 Aug 2016 13:36:31 +0000 Subject: [PATCH] Fixed a typo (compilation_commands.json --> compile_commands.json). git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@279240 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/HowToSetupToolingForLLVM.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/HowToSetupToolingForLLVM.rst b/docs/HowToSetupToolingForLLVM.rst index 924774210b..3812fc9f46 100644 --- a/docs/HowToSetupToolingForLLVM.rst +++ b/docs/HowToSetupToolingForLLVM.rst @@ -13,7 +13,7 @@ Introduction Clang Tooling needs a compilation database to figure out specific build options for each file. Currently it can create a compilation database -from the ``compilation_commands.json`` file, generated by CMake. When +from the ``compile_commands.json`` file, generated by CMake. When invoking clang tools, you can either specify a path to a build directory using a command line parameter ``-p`` or let Clang Tooling find this file in your source tree. In either case you need to configure your -- 2.40.0