Google Git
Sign in
bazel / bazel / acdb8e702e6a5e9181defd8c4ccdf90899261e1c
commitacdb8e702e6a5e9181defd8c4ccdf90899261e1c[log] [tgz]
authorGoogler <ilist@google.com>Mon Jan 15 07:30:32 2024 -0800
committerCopybara-Service <copybara-worker@google.com>Mon Jan 15 07:32:11 2024 -0800
tree9c9197d67b7b6e46c7c48cafb370f85fa8ba3e9d
parent95af3756a10c604d25e4a6fcf585a2f6d9b5038c [diff]
Change CppLinkAction to SpawnAction

Change LinkCommandLine to return CommandLines, method getCommandLines (similarly to Starlark actions).
Remove param file writing from CppLinkActionBuilder. CommandLines create the file automatically.
Pass the command lines into SpawnAction.
Remove unnecessary fields from fingerprint computation (most of them should already be removed in previous changes). toolchainEnv needs to stay, because it's used in getEffectiveEnvironment.

Most of the remaining public methods in LinkCommandLine and CppLinkAction should be removed. ATM they are still used in tests.

RELNOTES[INC]: CppLinkAction returns 2 args to aspects that have correct quoting set (before it was always 1 args object defaulting to bash escaping)

PiperOrigin-RevId: 598606687
Change-Id: Ib428b10c336c2f211fd5a4599d6d6ec57fb3f668
16 files changed
tree: 9c9197d67b7b6e46c7c48cafb370f85fa8ba3e9d
  1. .bazelci/
  2. .github/
  3. examples/
  4. scripts/
  5. site/
  6. src/
  7. third_party/
  8. tools/
  9. .bazelrc
  10. .bazelversion
  11. .gitattributes
  12. .gitignore
  13. AUTHORS
  14. bazel_downloader.cfg
  15. BUILD
  16. CHANGELOG.md
  17. CODE_OF_CONDUCT.md
  18. CODEOWNERS
  19. combine_distfiles.py
  20. combine_distfiles_to_tar.sh
  21. compile.sh
  22. CONTRIBUTING.md
  23. CONTRIBUTORS
  24. distdir.bzl
  25. extensions.bzl
  26. LICENSE
  27. maven_install.json
  28. MODULE.bazel
  29. MODULE.bazel.lock
  30. rbe_extension.bzl
  31. README.md
  32. repositories.bzl
  33. requirements.txt
  34. SECURITY.md
  35. WORKSPACE
  36. WORKSPACE.bzlmod
  37. workspace_deps.bzl
README.md

Bazel

{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.

Getting Started

Documentation

Reporting a Vulnerability

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.

Contributing to Bazel

See CONTRIBUTING.md

Build status