commit | 4b7f33905a9f8ff1027ef03c745274c4af9ec2ea | [log] [tgz] |
---|---|---|
author | Googler <noreply@google.com> | Thu Jun 16 10:35:13 2022 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Thu Jun 16 10:36:18 2022 -0700 |
tree | 58d4e9d4fd3fb8d80cdca488f5de25292e2ef53f | |
parent | 88627d7904bcc0747b2946233d0c706c5d325ea4 [diff] |
Automated rollback of commit 011b55099d1afcd590b42839a143f08a4a5cd9f3. *** Reason for rollback *** breaking blaze nightly 2022.06.16-1 *** Original change description *** Handle --objccopt in C++ Build API 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 are a couple slight changes 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. - Objective-C parse... PiperOrigin-RevId: 455416523 Change-Id: Iccf6f951a050e14cfd309debbce9352cc456e587
{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