Use prebuilt launcher_maker for Windows
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
PiperOrigin-RevId: 580200034
Change-Id: Ic5a65a5021ea8b0b325b68c1817180e429b6d56b
diff --git a/src/create_embedded_tools.py b/src/create_embedded_tools.py
index 1bac79f..edc987a 100644
--- a/src/create_embedded_tools.py
+++ b/src/create_embedded_tools.py
@@ -48,6 +48,7 @@
('*tools/cpp/runfiles/generated_*',
lambda x: 'tools/cpp/runfiles/' + os.path.basename(x)[len('generated_'):]),
('*launcher.exe', lambda x: 'tools/launcher/launcher.exe'),
+ ('*launcher_maker.exe', lambda x: 'tools/launcher/launcher_maker.exe'),
('*def_parser.exe', lambda x: 'tools/def_parser/def_parser.exe'),
('*zipper.exe', lambda x: 'tools/zip/zipper/zipper.exe'),
('*zipper', lambda x: 'tools/zip/zipper/zipper'),
