Re: [PATCH 2/3] cmake: create compile_commands.json by default
- From
Eric Sunshine <sunshine@sunshineco.com>
- Date
- Jun 4, 2021, 18:05 UTC
- Message-ID
- <CAPig+cS3SQTP=49jHxEuMahwqdCstD7Qgck2Oxkc35ZJkj_eYA@mail.gmail.com>
- In-Reply-To
- <c3bf266cf03a9678933623b48927ee749956218d.1622828605.git.gitgitgadget@gmail.com>
On Fri, Jun 4, 2021 at 1:44 PM Matthew Rogers via GitGitGadget <gitgitgadget@gmail.com> wrote:
Show 21 quoted lines
> Some users have expressed interest in a more "batteries included" way of > building via CMake[1], and a big part of that is providing easier access > to tooling external tools. > > A straightforward way to accomplish this is to make it as simple as > possible is to enable the generation of the compile_commands.json file, > which is supported by many tools such as: clang-tidy, clang-format, > sourcetrail, etc. > > This does come with a small run-time overhead during the configuration > step (~6 seconds on my machine): > [...] > This seems like a small enough price to pay to make the project more > accessible to newer users. Additionally there are other large projects > like llvm [2] which has had this enabled by default for >6 years at the > time of this writing, and no real negative consequences that I can find > with my search-skills. > > NOTE: That the comppile_commands.json is currenntly produced only when > using the Ninja and Makefile generators. See The CMake documentation[3] > for more info.
s/comppile/compile/ s/currenntly/currently/
> Signed-off-by: Matthew Rogers <mattr94@gmail.com>