[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>
diff --git a/third_party/pigweed b/third_party/pigweed
index 2e7d5a2..ca32950 160000
--- a/third_party/pigweed
+++ b/third_party/pigweed
@@ -1 +1 @@
-Subproject commit 2e7d5a25e1c63e5d38c14eb8ae706d70b0108ac1
+Subproject commit ca32950567adbdbcb0192258b8c61a7c636682b0
