| commit | 1f18b1911b28347157e9250deb5e223a3de3d032 | [log] [tgz] |
|---|---|---|
| author | Googler <wyv@google.com> | Mon Jun 12 12:23:56 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Jun 12 12:25:37 2023 -0700 |
| tree | c5cebeb60d42faaa9bdbc11ed1fe7e72ba93d6f1 | |
| parent | 343ab03d0c6e5828b498765cd83c80cb731b1e3d [diff] |
Add a PackageArgs class in preparation for REPO.bazel - Created a PackageArgs class that stores the values passed to the attrs of the `package()` function, so that they can be applied to a package builder in one go - These attr values used to be applied as soon as each attr is processed (i.e. evaluated). We can't do that anymore for repo(), since at the time of REPO.bazel evaluation, the package hasn't started being built yet. - Instead of storing the individual fields, Package now just holds on to a PackageArgs object. - In a follow-up CL, we store all the repo() values in a PackageArgs class, and apply those before the package() ones. - Also removed `Package#isDefaultVisibilitySet` as nobody calls it anymore. Work towards https://github.com/bazelbuild/bazel/issues/18077 PiperOrigin-RevId: 539728608 Change-Id: Ie4a081fa0e52e833ac2a6be50033f95728da3a9b
{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
