| commit | f785f28ee676707066ac81b8172b11e715d253f4 | [log] [tgz] |
|---|---|---|
| author | Googler <gnish@google.com> | Tue Mar 07 07:24:40 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Mar 07 07:26:16 2023 -0800 |
| tree | 519b0eeda4319f6e54b25d771a215b3c44a1e95b | |
| parent | d81fbc833aeca86dff5389f54822c754942a5ce5 [diff] |
Move C++ API to builtins in `cc_common.bzl`. Initially `cc_common.bzl` will serve as a wrapper on the native methods. This change makes it easier to gradually Starlarkify them. Relevant changes: * `CcModuleApi.java` is exposed to Starlark builtins as - `cc_common_internal_do_not_use` and is further restricted so that the symbol can only be called by `cc_common.bzl`. * Builtin restriction checks are moved from native code to Starlark. * `cc_common` toplevel symbol points to `cc_common.bzl` - which in turn wraps around native code. PiperOrigin-RevId: 514725933 Change-Id: I3db6e22c2f29db1fd7d863547b5bb1926255c9f3
{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
