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

roll: pigweed, pw_toolchain: pw_ide: Add option to process comp DBs by path

As an alternative to the current method of searching for compilation
databases in your source and build tree, this adds an option to
directly specify the path(s). This is particularly helpful for Bazel-
based projects for two reasons:

1. The predominant approach to generating compile commands in Bazel
   world is to just generate a single file with all commands in the
   root dir of the project, so there's no need to search for files.

2. By default, tooling runs within the Bazel environment, which could
   be located somewhere completely different from project checkout dir.
   So the search-based approach's assumptions of known source and build
   dirs breaks down.

Original-Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/pigweed/+/218334
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>

https://pigweed.googlesource.com/pigweed/pigweed
pigweed, pw_toolchain Rolled-Commits: 51ed6ec5209e23c..64f458827b65993
Roller-URL: https://ci.chromium.org/b/8744048389785160017
GitWatcher: ignore
CQ-Do-Not-Cancel-Tryjobs: true
Change-Id: I2a9fe22d62e072a7475c74884465aa8029799197
Reviewed-on: https://pigweed-review.googlesource.com/c/pigweed/quickstart/bazel/+/218491
Lint: Lint 🤖 <android-build-ayeaye@system.gserviceaccount.com>
Bot-Commit: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>
Commit-Queue: Pigweed Roller <pigweed-roller@pigweed-service-accounts.iam.gserviceaccount.com>