| commit | e3e530deb294a1241e3e14c80e8a54e28c96e3af | [log] [tgz] |
|---|---|---|
| author | Googler <ilist@google.com> | Thu May 02 07:24:44 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu May 02 07:25:59 2024 -0700 |
| tree | 9198a139750b7a0faad802b2414e8c9109757603 | |
| parent | ab11e400549a57627810852a468be3c7c3b3f776 [diff] |
Replace CppLinkAction in tests with SpawnAction This makes it possible to run the same tests over Starlark version of CppLinkAction. Starlark rules create general SpawnActions. The change was mostly done by search and replace and is a no-op. Implement getLinkCommandLine so that it casts command line from the spawn action. This approach work both before and after the code is in Starlark. Remove getLinkCommandLineForTesting from CppLinkAction. It is is not needed anymore. Implement getAction(mnemonic) in BuildViewTest case. This is a stable way to retrieve a specific action created in Starlark. PiperOrigin-RevId: 630056081 Change-Id: I3c322d405a860bfa035da879270af42b81aa3fcc
{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
