| commit | ebb12e832d115080c5dbfc5d47ebc77e9134c489 | [log] [tgz] |
|---|---|---|
| author | plf <plf@google.com> | Wed Jul 28 05:56:45 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jul 28 05:57:56 2021 -0700 |
| tree | 37a809ca54f6acb6d3d9f553dac53915ac18d447 | |
| parent | 5ac18cd7c545e67ba1cef86d30fa7cca167aad11 [diff] |
Refactor apple_static_library use of split transition The current way the native code is written cannot be re-written to Starlark. It looks like everything that cannot be done in Starlark can be refactored away. Mainly, the code used to pass the build configuration from each of the list of transitioned deps to lower level APIs that were using that configuration to for example build artifacts in a specific directory (which is unnecessary). In Starlark an action can only output to the directory of the current configured target. RELNOTES:none PiperOrigin-RevId: 387330041
{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:
See CONTRIBUTING.md
