commit | 555772b3eb2e15c22fdd253f02d8e443e5947c0b | [log] [tgz] |
---|---|---|
author | hlopko <hlopko@google.com> | Thu Oct 18 02:17:37 2018 -0700 |
committer | John Cater <jcater@google.com> | Wed Nov 14 13:08:19 2018 -0500 |
tree | 2fc3b92938c4c0e18304a0a3cb586c61052b578e | |
parent | eb2af0f699350ad187048bf814a95af23f562c77 [diff] |
Also update cc_toolchain.toolchain_identifier when CC_TOOLCHAIN_NAME is set Since we specify toolchain_identifier in cc_toolchain now, it is much more strict in selecting a CROSSTOOL toolchain. This broke when CC_TOOLCHAIN_NAME environment variable was set, as that only renamed toolchain identifier in the CROSSTOOL, but not in the cc_toolchain. This cl fixes that. This fixed https://github.com/bazelbuild/bazel-toolchains/issues/198. RELNOTES: None PiperOrigin-RevId: 217666695
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel only rebuilds what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
See CONTRIBUTING.md
Bazel is released in ‘Beta’. See the product roadmap to learn about the path toward a stable 1.0 release.