tree 87f92ef8ec677fe3d16ce5f876ed11c55b0b3465
parent 5edda56502f8651a4220320cfdd73304162e9389
author bazel.build machine account <15028808+bazel-io@users.noreply.github.com> 1699379525 -0500
committer GitHub <noreply@github.com> 1699379525 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJlSnlFCRBK7hj4Ov3rIwAAcPoIABz+7ZytSQRPjphmelUNWpbt
 FxeClWMQS4kE5vWlyPDJvzaKaV1q+F78mMUKjdfzUnzpzGHNndLZgyYqauX2kxrr
 ULGwBhspM62RaE6CN+3yH7i1DNuCv0SpNKFa2djyMtIjT/IUfmbRAvoXoeWyQz6f
 yDZsP+A0RbeijB0wyTT3j0OS7TI70/Rp8xGZNa5fo0qYN6vo6RVstFGG/n1vJ0KB
 G6FstMJEYlwjAIlG8pVgc+fjlnkpQDbcZLKV5ZfVyjBpKF3bL3BEJ0421DQyTSUy
 HfR9T4DKZ3Q8JUK+t0q63dYY+HsIFYpqDHVAohtgQD1UQkEIsCRMa9JZnkjVyHY=
 =/8HZ
 -----END PGP SIGNATURE-----
 

[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>