| commit | 4e7ed50345f3a3037549f7c41f852b5d9db4a08d | [log] [tgz] |
|---|---|---|
| author | Brian <bsilver16384@gmail.com> | Mon Sep 28 12:58:42 2015 +0000 |
| committer | Kristina Chodorow <kchodorow@google.com> | Mon Sep 28 14:35:33 2015 +0000 |
| tree | 29f8409ad033443e0f146696aa00736cec619a55 | |
| parent | 8fcfbe820485d2f81441bef199f853303400a190 [diff] |
Fix broken build under Debian Wheezy. With the toolchain under Wheezy (GCC 4.7.2 and binutils 2.22), using both -fPIE and -fPIC does not create pic object files, which the build of Bazel seems to expect as of ee8fcd312eef51d2558c940f00d6381af0d52dff. -- Change-Id: I0a33d1bc6dc0e3cdcffb473d4e78dac1a6b8ab41 Reviewed-on: https://bazel-review.googlesource.com/#/c/1690/ MOS_MIGRATED_REVID=104093416
{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.