commit | cf8f94df589aa40b9389ab83da0869ab83d508d7 | [log] [tgz] |
---|---|---|
author | bazel.build machine account <15028808+bazel-io@users.noreply.github.com> | Tue Nov 07 12:52:05 2023 -0500 |
committer | GitHub <noreply@github.com> | Tue Nov 07 17:52:05 2023 +0000 |
tree | 87f92ef8ec677fe3d16ce5f876ed11c55b0b3465 | |
parent | 5edda56502f8651a4220320cfdd73304162e9389 [diff] |
[7.0.0] Bazel 7.0 - can't compile with `/DUNICODE` `/D_UNICODE` (#20083) Using a prebuilt binary solves a few issues: * Avoids having to build the launcher maker entirely. It is special purpose binary, isn't going to change much, and would otherwise incur needing a C++ toolchain. * It doesn't work with `--host_copt=/DUNICODE`, as described in #19977 * Preserves behavior of Starlarkified rules that use the launcher maker. The non-Starlark implementation used a special Java-implemented action to replicate what launcher_maker does, thus avoiding the C++ toolchain dependency. Fixes #19977 Commit https://github.com/bazelbuild/bazel/commit/f898da56995809140b65d2b3b6f5b631a3ec511a PiperOrigin-RevId: 580200034 Change-Id: Ic5a65a5021ea8b0b325b68c1817180e429b6d56b Co-authored-by: Richard Levasseur <rlevasseur@google.com>
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only 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:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md