tree 40282cd412a1adc46cd530b40c9a3bde053a7cd3
parent 2e7d5a25e1c63e5d38c14eb8ae706d70b0108ac1
author Chad Norvell <chadnorvell@google.com> 1663377753 +0000
committer CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> 1663377753 +0000

pw_ide: Manage C++ compilation DBs

GN and other build systems can generate clangd compilation databases
(compile_commands.json) for Pigweed projects, but because these projects
usually have multiple targets/toolchains, as well as targets that aren't
actually clang/GCC compile commands (e.g. Python wrappers for code
analysis), those files won't work reliably with clangd without
processing. Processing yields several consistent and valid compilation
databases, one for each valid target. Additional tools allow selection
of which compilation database clangd should use via a stable symlink in
the working directory.

Change-Id: Ib13155feca7e8a056b4b32a0d54ce0a179f1cace
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/110253
Reviewed-by: Anthony DiGirolamo <tonymd@google.com>
Commit-Queue: Chad Norvell <chadnorvell@google.com>