commit | 6846317fded0de1e404ae02de822e9188b0866b6 | [log] [tgz] |
---|---|---|
author | Googler <ilist@google.com> | Fri Dec 29 04:07:51 2023 -0800 |
committer | Copybara-Service <copybara-worker@google.com> | Fri Dec 29 04:09:34 2023 -0800 |
tree | 626584edfaed676ed66f686b8b7dff20ae25edd6 | |
parent | 87e46aed3e58e913bb5b9a58efba16018b3757bd [diff] |
Remove linkerInputArtifacts from LinkCommandLine They value of linkerInputArtifacts was only used in tests. Replace uses in tests with CppLinkCommand.getInputs(). The second method also returns path to linker and some scripts used during linker, so exact comparisons need to be replaced with containsAtLeast. It's more reliable on one hand (because actions can't lie about their inputs), and less reliable (because there could be some additional files on the path that are weren't there before). However, general intent of the tests is verifying that the files are present. PiperOrigin-RevId: 594431021 Change-Id: I84cdda8d4bc50715ea3e412760bf8c713abd0353
{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