Remove legacy parameters from cc_common.create_cc_toolchain_config_info().

Exception is the need_pic field, until we figure out its story.

Dynamic linking depends on the presence of "dynamic_linking_mode" feature.

List of removed fields:                     | What we pass to CcToolchainConfigInfo
                                            | constructor instead:

supports_gold_linker                        | check for corresponding feature
supports_start_end_lib                      | check for corresponding feature
supports_interface_shared_objects           | check for corresponding feature
supports_embedded_runtimes                  | check for corresponding feature
supports_fission                            | check for corresponding feature
supports_dsym                               | unused, pass 'false'
static_runtime_filegroup                    | pass empty string
dynamic_runtime_filegroup                   | pass empty string
compiler_flags                              | pass empty list
cxx_flags                                   | pass empty list
unfiltered_cxx_flags                        | pass empty list
linker_flags                                | pass empty list
dynamic_library_linker_flags                | pass empty list
test_only_linker_flags                      | pass empty list
objcopy_embed_flags                         | pass empty list
ld_embed_flags                              | pass empty list
compilation_mode_compiler_flags             | pass empty list
compilation_mode_cxx_flags                  | pass empty list
compilation_mode_linker_flags               | pass empty list
mostly_static_linking_mode_flags            | pass empty list
dynamic_linking_mode_flags                  | pass empty list
fully_static_linking_mode_flags             | pass empty list
mostly_static_libraries_linking_mode_flags  | pass empty list
default_libc_top                            | pass empty string

Work towards issue #5380
RELNOTES: None.
PiperOrigin-RevId: 225978244
3 files changed
tree: 550a57a812f456a02a9002d64f54a42cd8a866ed
  1. .bazelci/
  2. examples/
  3. scripts/
  4. site/
  5. src/
  6. third_party/
  7. tools/
  8. .gitattributes
  9. .gitignore
  10. AUTHORS
  11. BUILD
  12. CHANGELOG.md
  13. CODEOWNERS
  14. combine_distfiles.py
  15. combine_distfiles_to_tar.sh
  16. compile.sh
  17. CONTRIBUTING.md
  18. CONTRIBUTORS
  19. distdir.bzl
  20. ISSUE_TEMPLATE.md
  21. LICENSE
  22. README.md
  23. WORKSPACE
README.md

Bazel

{Fast, Correct} - Choose two

Build and test software of any size, quickly and reliably.

  • Speed up your builds and tests: Bazel only rebuilds 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

Contributing to Bazel

See CONTRIBUTING.md

Build status

Bazel is released in ‘Beta’. See the product roadmap to learn about the path toward a stable 1.0 release.