| commit | 8d22e466602af98486c2cfa1a5fb4819f07ad188 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Tue Mar 15 03:09:13 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Mar 15 03:10:43 2022 -0700 |
| tree | 53cb9e04b9512a0030d85907c74f3f0a419cb281 | |
| parent | f789c0d8dde1e7b5314adcf0de40a693b47f2d50 [diff] |
Add implementation of collect_compilation_prerequisites to cc_helper, this makes cc_internal's collect_compilation_prerequisites method obsolete. Add test for cc_binary rule to test compilation prerequisites of OutputGroupInfo. Expose API from CcCompilationContext necessary for Starlark transliteration. Add builtin privacy tests for added methods. CC_AND_OBJC constant's extensions now match native version. Fix a bug where _check_src_extension would always return True if the file extension matched shared and versioned shared libraries(even if we did not want to include them), required a refactor of the code. This has not been noticed since the two consumers of the method(cc_binary & cc_library) allow shared and versioned shared libraries. PiperOrigin-RevId: 434702440
{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
