Update Rust new_http_archive rules to use 1.4 and strip_prefix
The lack of strip_prefix lead to the files not being found with the
supplied rust.BUILD file.
Tested:
- created simple repository with rust_library and rust_binary
targets as outlined in
//tools/build_rules/rust/README.md
- (workaround) copied //tools/build_rules/rust/rust.BUILD into workspace as
suggested by @kchodorow:
https://github.com/bazelbuild/bazel/issues/488#issuecomment-143754576
- verified that library and binary build, and that binary runs
correctly
RELNOTES: Update Rust to 1.4
--
Change-Id: Ic2c275395ca245179e35e723faf0b9d13120fa1f
Reviewed-on: https://bazel-review.googlesource.com/#/c/2382/
MOS_MIGRATED_REVID=109187409
{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.