| commit | 6e2ccb75d7c9e1e9102a0512449381e2fffc57a7 | [log] [tgz] |
|---|---|---|
| author | Laszlo Csomor <laszlocsomor@google.com> | Wed Mar 01 16:53:35 2017 +0000 |
| committer | Yue Gan <yueg@google.com> | Wed Mar 01 17:20:57 2017 +0000 |
| tree | ed1d6e22971d4312f2370211638aeb2381374c2e | |
| parent | 0dff43a2e3c566766f64fed597d143885d5d8368 [diff] |
Bazel client: simplify {Read,Write}File semantics
Introduce a platform-specific file handle type
(HANDLE on Windows, int on Linux/Darwin/FreeBSD)
so we can get rid of the read_func and write_func
functions, since they are always the same
everywhere.
Also include file_platform.h in file.h, since they
are logically the same file (file_platform.h is
just the platform-specific part of file.h).
--
PiperOrigin-RevId: 148892736
MOS_MIGRATED_REVID=148892736
{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.