| commit | ffb5c6c63dc9671791c416558ea3da297aa99f77 | [log] [tgz] |
|---|---|---|
| author | Damian Banki <ddaniel.banki@gmail.com> | Thu Jan 08 22:17:16 2026 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jan 08 22:19:56 2026 -0800 |
| tree | df41df144738f4e3f506d92b4bfa17eedd5151fe | |
| parent | a996ae1024180194599e6cd7b418de6faccff053 [diff] |
Add flags to disable Apple and Objc configuration fragments. This change introduces `--incompatible_remove_ctx_apple_fragment` (tracked in #28081) and `--incompatible_remove_ctx_objc_fragment` (tracked in #28082). When set to true, these flags cause AppleConfiguration and ObjcConfiguration, respectively, to be excluded from the build context, making `ctx.fragments.apple` and `ctx.fragments.objc` undefined. This is a step towards migrating Apple build flags from core Bazel fragments to be defined within Apple rules. This is precursor work for https://github.com/bazelbuild/rules_apple/issues/2845 Also see: [Starlarkify Apple flags](https://docs.google.com/document/d/1k2w0QadZUfymFtwCBtdsA6MBs0eExFZ9l08KtFQM4Es/edit?tab=t.0#heading=h.9wqxvqh3dnld) [Starlarkify native Bazel flags](https://docs.google.com/document/d/1yOvi4hVV7Ja32ocwVb4lsEUnijftk8nilXPncYm-BH8/edit?tab=t.0#heading=h.5mcn15i0e1ch) (proposal) Closes #28083. PiperOrigin-RevId: 854027377 Change-Id: Ida013755c28656c3017960a4cc1909a08f9085bc
{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
