| commit | 280ae1a8bc01bc26c7ba85453921b3c2b7073ac0 | [log] [tgz] |
|---|---|---|
| author | Googler <waltl@google.com> | Thu Jan 19 09:40:48 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jan 19 09:42:18 2023 -0800 |
| tree | 71b3a07bb4a7a6d662c84c1932866025443b0330 | |
| parent | bfa72889ec6cb9bfb359226124c43ecffa44b078 [diff] |
Allow tree artifacts in source attributes to have arbitrary extensions Currently, tree artifacts in srcs/hdrs/non_arc_srcs need to have extensions that match their contents, which is unnecessary and silly. The new behavior mirrors how cc_library behaves. This change also imports a check in cc_library that checks that a source file is not duplicated -- this may cause blaze to error out when it previously wouldn't. The fix is simply to deduplicate the list of source files. This requires way more code factoring that it should, but the final result gets objc_library closer to cc_library and hopefully is easier to maintain. We were able to add functionality while deleting more code than we add (if we don't count tests). PiperOrigin-RevId: 503189010 Change-Id: I9a20a71753183527b7c0391b94968d7acd6de1a4
{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
