| commit | 9c1090bcd88f187e8849a08fa7cd42246a9b5095 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Sat Oct 08 07:49:02 2016 +0000 |
| committer | Yue Gan <yueg@google.com> | Mon Oct 10 09:54:49 2016 +0000 |
| tree | f6fb330e50ca726797cbc43e2c6eda6538486dfe | |
| parent | 2837781bb9613958eba289ce1e2608dffeb6bf6e [diff] |
Fall back to compiling header-only libraries with --compile_one_dependency. In toolchains that support parse_headers, this is the desired action. For other toolchains, this change makes blaze try to build a header-only library which creates the error that the header only library is not a supported target kind. Seems like either error message is not useful/actionable. In theory, it would be better to actually analyze whether a parse_headers is activated, but that requires refactoring a lot of code that is currently C++ specific. -- MOS_MIGRATED_REVID=135554761
{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.