From d0e9a3962268dd32b8f1c18e9dfbaf018faea2c3 Mon Sep 17 00:00:00 2001 From: Freaxed Date: Tue, 23 May 2023 15:33:32 +0000 Subject: [PATCH] Update Configuring-clangd-lsp.md --- Configuring-clangd-lsp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Configuring-clangd-lsp.md b/Configuring-clangd-lsp.md index 40c23727..b8fd40aa 100644 --- a/Configuring-clangd-lsp.md +++ b/Configuring-clangd-lsp.md @@ -17,7 +17,7 @@ Two main configuration point: ## The project To let understand clangd how you want each file to be compiled, you should provide a compile database file (compile_commands.json). -The file contains, for each file of the project, the list off all the flags and include paths your compiler needs. +The file contains, for each file of the project, the list of all the flags and include paths your compiler needs. There are usefull tools to let you create the compile_commands.json file automatically from a building tool like make, jam or cmake. Usually this is enough to let clangd work correctly in most cases.