Google Git
Sign in
bazel / bazel / 998f4fe43361f0749097428fc7e421b44248271d
commit998f4fe43361f0749097428fc7e421b44248271d[log] [tgz]
authorGoogler <ilist@google.com>Wed May 08 05:36:10 2024 -0700
committerCopybara-Service <copybara-worker@google.com>Wed May 08 05:39:54 2024 -0700
tree01df6f1dd6085de0f24b32bbfec7912edc0185b8
parent8f523863817592fa4c563b6f318df06621c675bc [diff]
Rewrite LinkBuildVariables class and create_link_variables to Starlark

Rewrite cc_common.create_link_variables to Starlark and wire it into cc_common.

Split out cc_helper into cc_helper_internal. That is to break a cycle: cc_common.bzl -> cc_common.create_link_variables -> cc_helper.bzl -> cc_common.bzl.

Create cc_internal.cc_toolchain_variables and add build_variables_dict to cc_toolchain. Natively, build variables are wrapped into CcToolchainVariables. In new Starlark code, we can use a simple dict most of the time and wrap it where it's needed.

Expose intrenally get_artifact_name_extension_for_category. It's used in the link_variables.

Expose cpp_config.cs_fdo_instrument. It's used in link_variables.

PiperOrigin-RevId: 631768401
Change-Id: I12a23e72aa459601cccd5fe5fe442ab60705e3e8
15 files changed
tree: 01df6f1dd6085de0f24b32bbfec7912edc0185b8
  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