| commit | ee38b630272128376b4491d794ee28ca0e871f9d | [log] [tgz] |
|---|---|---|
| author | plf <plf@google.com> | Thu Dec 09 07:16:48 2021 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Dec 09 07:18:10 2021 -0800 |
| tree | 0d1b8440ab6ca2b06b5aed38047b23b99c06025b | |
| parent | 005361c895da334beb873901e93aff06d180256e [diff] |
Add Starlark mechanism for default_copts and defaults_hdrs_check We add a new native computed default class which can only be seen from builtins. This ensures that not only are we able to get the value of default_copts and default_hdrs_check as set in the package() rule, but that when the values in package() changes, the dependency server is able to compute the affected targets properly. This is not a long term mechanism and should be replaced by something more generic as described in b/200065655#comment3 This CL also adds two additional methods to CcStarlarkInternal, init_make_variables and create_linkstamp. RELNOTES:none PiperOrigin-RevId: 415258162
{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
