Implements an attribute 'features' that allows overriding package level
features.

Features on the rule level modify features that are enabled at the package
level. Note that this behavior is different from how the current command line /
package level interaction is, but we probably want to change the command line
behavior.

Alternative implementations considered:
a) using package-level features as default value for the rule attribute; this
   would make it hard for future transitions; adding a completely new feature
   to a package should not require updating all rules that have overrides
b) putting all positive features and all negative features from command-line,
   package, and rule attribute into a positive and negative set, and subtract
   the negative from the positive set; this is how the command-line features
   worked previously, but it makes it impossible to enable a features that
   is disabled at the package level just for one rule.

RELNOTES: Add 'features' attribute on the rule level.

--
MOS_MIGRATED_REVID=92448449
4 files changed
tree: bbc33930ada4ef0c182c206c188f84b04213247c
  1. .travis/
  2. examples/
  3. scripts/
  4. site/
  5. src/
  6. third_party/
  7. tools/
  8. .gitignore
  9. .travis.yml
  10. bootstrap_test.sh
  11. compile.sh
  12. CONTRIBUTING.md
  13. LICENSE.txt
  14. README.md
  15. WORKSPACE
README.md

Bazel (Alpha)

{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

Build Status