tree ea7aae9e1bad2bcd4d9010bd4674da2bb44bf3b6
parent 7ca2d2eb0d69e2a8de2606edb3f265203e280c18
author Chad Norvell <chadnorvell@pigweed.infra.roller.google.com> 1663378120 +0000
committer CQ Bot Account <pigweed-scoped@luci-project-accounts.iam.gserviceaccount.com> 1663378120 +0000

[roll third_party/pigweed] 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.

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/110253

https://pigweed.googlesource.com/pigweed/pigweed
third_party/pigweed Rolled-Commits: 2e7d5a25e1c63e5..ca32950567adbdb
Roller-URL: https://ci.chromium.org/b/8802815691319120289
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: Ic0d56c4af921b546b3c71616f6332452cddff745
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/experimental/+/110730
Commit-Queue: Pigweed Integration Roller <pigweed-integration-roller@pigweed.google.com.iam.gserviceaccount.com>
Bot-Commit: Pigweed Integration Roller <pigweed-integration-roller@pigweed.google.com.iam.gserviceaccount.com>