commit | da20a73e6f8a8e4fa1ac15ee345d70ea92647e46 | [log] [tgz] |
---|---|---|
author | Laszlo Csomor <laszlocsomor@google.com> | Thu Jan 12 12:40:42 2017 +0000 |
committer | Marcel Hlopko <hlopko@google.com> | Thu Jan 12 14:08:35 2017 +0000 |
tree | f5f24179f89f355e8a51d7668236c49679111fa3 | |
parent | c828053419d41bfe9377bcb5a01032c00800308a [diff] |
Windows, JNI: arg for argv0 in nativeCreateProcess Add a separate argument to nativeCreateProcess for argv[0] specifically, and another for the rest of the args. In a subsequent change I'll add code to compute the 8dot3 style short name of the argv[0] so we can use longer paths for executables in CreateProcessA than we normally could. This is the same approach as used in commit 44ecf9a0c7c25496a43f59f1c8f20df9527e12cb See https://github.com/bazelbuild/bazel/issues/2107 See https://github.com/bazelbuild/bazel/issues/2181 -- PiperOrigin-RevId: 144311562 MOS_MIGRATED_REVID=144311562
{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.