bazelbuild / bazelbuild/rules_java
Windows: statically link msvcrt into Java Tools
- Lenguaje dominante
- Starlark
- Estrellas
- 103
- Forks
- 102
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
Hi!
On Windows, the prebuilt tools in `remote_java_tools_windows` require the Microsoft VC++ Redistributable, for example:
```
external\rules_java++toolchains+remote_java_tools_windows\java_tools\ijar\ijar.exe
external\rules_java++toolchains+remote_java_tools_windows\java_tools\src\tools\singlejar\singlejar_local.exe
external\rules_java++toolchains+remote_java_tools_windows\java_tools\turbine_direct_graal.exe
```
Without the redist installed, these fail due to missing `msvcp140.dll`, `vcruntime140.dll`, `vcruntime140_1.dll` (exit code `-1073741515`).
Would it be possible link the MSVC runtime statically (i.e., `--features=static_link_msvcrt`) for these binaries, or ship the required VC++ runtime DLLs app‑local alongside the executables?
Related issue: https://github.com/bazelbuild/bazel/issues/8328.
Guía de contribución
Línea de trabajo
Start by examining how the Windows binaries under remote_java_tools_windows are produced, especially ijar.exe, singlejar_local.exe, and turbine_direct_graal.exe. Reproduce the failure on a Windows machine without the Microsoft VC++ Redistributable, then verify that the chosen packaging or linking change lets all three tools run without those missing DLLs.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- java
- Área
- build-system
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100