| commit | fbc546b2850d95094ddbbded2e2bd36312e26248 | [log] [tgz] |
|---|---|---|
| author | Laszlo Csomor <laszlocsomor@google.com> | Fri Jan 20 10:10:56 2017 +0000 |
| committer | Vladimir Moskva <vladmos@google.com> | Fri Jan 20 12:21:46 2017 +0000 |
| tree | cdf9c793506b475a9126555c090618a2471635da | |
| parent | c051fafd957dcd3c6f11db14589c10b924d90157 [diff] |
Windows, JNI, refactor: co-locate all JNI code Move JNI code from windows_file_operations.cc to windows_processes.cc, so all the JNI code is now in the latter. This lets us expose windows_file_operations.* to the Bazel client (via the ":windows_jni_lib" target), so we can finally share file handling logic between the Bazel client and the JNI library. See https://github.com/bazelbuild/bazel/issues/2107 -- PiperOrigin-RevId: 145063140 MOS_MIGRATED_REVID=145063140
{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.