| commit | 5d2c97a61382ef2884abe1c341cec3a8b26ecdb0 | [log] [tgz] |
|---|---|---|
| author | Chris Sauer <cpsauer@users.noreply.github.com> | Thu Jul 27 11:10:08 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jul 27 11:11:20 2023 -0700 |
| tree | 1f68fd8732b86775cbfdef7e20a9f624a9462b6f | |
| parent | f309e0fc7fefa5d597db0b2dec7762e5523b69e7 [diff] |
Add new NDK rules to the NDK docs Hi wonderful Bazelers, I'd happened to notice that the new NDK rules weren't referenced from the NDK docs, so I thought I'd toss up a quick change to help new users find their way. Thanks for your consideration! Feel free (of course) to edit or push a different change if you'd prefer something else. (Was trying to strike a balance between the new rule being in their early stages and the old rule no longer being updated and not working for the past few years of NDKs. See https://github.com/bazelbuild/bazel/issues/12889 for more context.) Thanks, Chris (ex-Googler, [compile_commands_extractor](https://github.com/hedronvision/bazel-compile-commands-extractor/issues) author, rules_boost collaborator, etc.) Closes #18523. PiperOrigin-RevId: 551585249 Change-Id: Ida162f086657673e0c2cd884afc59107bc539f8e
{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
