| commit | 8a1584e77c5c71e98a8cac87e6c5df6ee5d94c63 | [log] [tgz] |
|---|---|---|
| author | Googler <allevato@google.com> | Wed Apr 17 05:44:26 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Apr 17 05:46:39 2024 -0700 |
| tree | 84738996a883b4713d5b59a8b9775e7262152729 | |
| parent | 445dfab8fdd7671fe6206ea938ef119c228019f0 [diff] |
Migrate `AvailableXcodesInfo`, `XcodeProperties`, and `XcodeVersionRuleData` to builtin Starlark (with Starlark-consistent names). The names of these things being very similar is likely to be confusing in the future, but we can address that after we've migrated them to apple_support. Fortunately they're only really used to communicate between the Xcode rules internally, so refactoring them shouldn't have many downstream effects. This change does not cover `XcodeConfigInfo`, since it's a bit more complicated. PiperOrigin-RevId: 625652603 Change-Id: Ic3c024f4b4f60c8fa93f68aa61e939215c965227
{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
