Add all transitive module maps when we use header modules.

When we have a library 'a' that depends on a library 'm' via multiple other
libraries, and 'm' is built as a module, we need clang to load the module
map of 'm'.
There are multiple possible solutions:
1. (This CL): Add all transitive module maps as inputs when we want to use
   a module map (at any transitive level). Clang will load all module maps,
   and find the corresponding modules.
2. Add the module maps of all top-level modules (e.g. modules that are not
   reached transitively through another module) to clang's command line (we
   already pass all transtitive module maps for each library that is compiled
   as a module).

The upside of (1) is that it simplifies the module map input computation and
removes some differences between remote and local compiles (local compiles will
always see all transitive module maps).
The upside of (2) would be that we use fewer module map inputs when we do
builds that use modules as long as we only have a small subset of libraries
at the bottom of the stack compiled as modules.
Both alternatives keep transitive module maps out of the inputs for actions
that do not use header modules, thus making sure the normal case does not
regress.

We are implementing (1) because the main slow-down with transitive module maps
is during the early loading phase, and should be quickly offset by module
builds. We will revisit that decision once we have more data.

--
MOS_MIGRATED_REVID=98118092
2 files changed
tree: baf1bfa0d6e955473d94c407255be41fc17daf9e
  1. .travis/
  2. examples/
  3. scripts/
  4. site/
  5. src/
  6. third_party/
  7. tools/
  8. .gitattributes
  9. .gitignore
  10. .travis.yml
  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