Add action_config and feature for linking on Windows

Also implemented whole archive feature on Windows

1. Pulled action_configs and features from CppLinkActionConfigs.java

2. Deleted many features not working on Windows. (AFAIK)
   including:
       symbol_counts
       output_execpath_flags_executable
       global_whole_archive_open
       runtime_root_flags
       global_whole_archive_close
       force_pic_flags

3. Added c++-link-interface-dynamic-library action config
   Not sure there is such thing on Windows, but it's currently in MANDATORY_LINK_TARGET_TYPES

4. Added build variable "whole_archive_object_files_params"

5. Automatically detect if linker supports /WHOLEARCHIVE and use the corresponding build variable

--
Change-Id: I232798a0eb1a3291f972b313a81e678b0121d58c
Reviewed-on: https://bazel-review.googlesource.com/#/c/6414
MOS_MIGRATED_REVID=135342093
4 files changed
tree: 8ac770d5470588c0cdcf7fb4e23eb063de4bb02a
  1. examples/
  2. scripts/
  3. site/
  4. src/
  5. third_party/
  6. tools/
  7. .gitattributes
  8. .gitignore
  9. AUTHORS
  10. BUILD
  11. CHANGELOG.md
  12. compile.sh
  13. CONTRIBUTING.md
  14. CONTRIBUTORS
  15. LICENSE.txt
  16. README.md
  17. WORKSPACE
README.md

Bazel (Beta)

{Fast, Correct} - Choose two

Bazel is a build tool that builds code quickly and reliably. It is used to build the majority of Google‘s software, and thus it has been designed to handle build problems present in Google’s development environment, including:

  • A massive, shared code repository, in which all software is built from source. Bazel has been built for speed, using both caching and parallelism to achieve this. Bazel is critical to Google's ability to continue to scale its software development practices as the company grows.

  • An emphasis on automated testing and releases. Bazel has been built for correctness and reproducibility, meaning that a build performed on a continuous build machine or in a release pipeline will generate bitwise-identical outputs to those generated on a developer's machine.

  • Language and platform diversity. Bazel's architecture is general enough to support many different programming languages within Google, and can be used to build both client and server software targeting multiple architectures from the same underlying codebase.

Find more background about Bazel in our FAQ.

Getting Started

About the Bazel project: