| commit | 02cbcd2cf0ace5479e43228ffc7ceab6853d4cff | [log] [tgz] |
|---|---|---|
| author | Greg Estren <gregestren@gmail.com> | Mon Oct 19 12:15:13 2020 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Oct 19 12:16:11 2020 -0700 |
| tree | 0b1d3e1c504b65bdd5b6b74d1fba0235572ab1ba | |
| parent | 2300e6d067858edfe2e3a8784daaab00bc841329 [diff] |
Implement cquery --output=graph Thankfully, `query` already has most of the infrastructure necessary to make this easy. query implements graph output (in `GraphOutputFormatter`) over a `Digraph<Target>`, which is a generic graph data structure with `Target` payloads. All output logic then runs over this data structure. To opt query in, all we have to do is create an equivalent `Digraph<ConfiguredTarget>`, which is a simple transformation from the backing graph. This change creates a new generic class for that common logic: `GraphOutputWriter`. query's `GraphOutputFormatter` then becomes a simple wrapper over that, and the new `GraphOutputFormatterCallback` is cquery's equivalent. A few differences: - cquery output is always fully ordered (`--order_output=full`). We could match this with query's controllable version, but I don't see a reason to make this yet another bit to configured. - query output annotates edges with select() conditions. cquery doesn't do this because select()s are resolved and removed from the graph after analysis. I think we could annotate edges with the *chosen* condition if there was demand, but that'd be a followup effort. Fixes https://github.com/bazelbuild/bazel/issues/10843 (for `cquery`, not `aquery`) Closes #12248. PiperOrigin-RevId: 337907070
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
See CONTRIBUTING.md
