| commit | 8c590d8941e8581ceb502d7ae190b0e5fa480b67 | [log] [tgz] |
|---|---|---|
| author | Googler <waltl@google.com> | Mon Jun 20 14:08:44 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Jun 20 14:10:10 2022 -0700 |
| tree | 0f6f946b87a073bfde762cb000dfcd567c20f458 | |
| parent | d26ecc8560908282aa3d64a675ee2019db89f9d7 [diff] |
Handle --objccopt in C++ Build API (try 2) This requires moving the required information from ObjcConfiguration to CppConfiguration. CppConfiuration.objccopts now has the same information as ObjcConfiguration.copts, and we can eventually delete the latter. There is one slight change in behavior: - C/C++ sources in objc_library will no longer get the options from --objccopt. This matches the behavior of other copts variants which are all done based on file extensions. Unlike the first try, we preserve the behavior of passing --objccopt to objc headers. PiperOrigin-RevId: 456121311 Change-Id: I6e965445e257c19eccb70d4ad600f159c1473f37
{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
