| commit | 9b30bf761a7526433c56251c49d7da3b8286bf8b | [log] [tgz] |
|---|---|---|
| author | Sam McCall <sammccall@google.com> | Wed Oct 04 02:16:45 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Oct 04 02:17:54 2023 -0700 |
| tree | fbf5c3c38e701b08d43f20e12d8bd3146af214e0 | |
| parent | ac10bac23bd138f64b071749e10b03fe22df333e [diff] |
Add module_files output group, used to build PCMs from cc_library etc directly Today, `bazel build :target` on a cc_library will not build its PCM. To debug problems with module compiles we resort to building a target that depends on the module. This gets in the way, particularly when a *minimal* such target doesn't exist and others need to reproduce the failure. With this change, `bazel build :target --output_groups=module_files` will produce the PCM. PiperOrigin-RevId: 570629210 Change-Id: Ic07509da42637321a0c65f41b0bba8864e3b6a83
{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:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
